Thanks for your help!! That goes for all the people who responded on the thread! :)
Turns out, I just didn't understand what the vmlinux part meant. Being totally new to linux, I just thought that was the required syntax for using gdb with qemu. I didn't realize it was supposed to be the name of t
On Thu, Jul 20, 2006 at 11:04:01PM +0200, Fabrice Bellard wrote:
> Daniel Jacobowitz wrote:
> >On Wed, Jul 19, 2006 at 08:43:57AM +, Steve Ellenoff wrote:
> >
> >>#3) Anytime I try to dump the instruction at the current IP such as:
> >>(gdb) x /10i $eip
> >>
> >>I get this - which means it's no
Daniel Jacobowitz wrote:
On Wed, Jul 19, 2006 at 08:43:57AM +, Steve Ellenoff wrote:
#3) Anytime I try to dump the instruction at the current IP such as:
(gdb) x /10i $eip
I get this - which means it's not actually reading or displaying the memory
properly, since those look to be what you
On Wed, Jul 19, 2006 at 08:43:57AM +, Steve Ellenoff wrote:
> #3) Anytime I try to dump the instruction at the current IP such as:
> (gdb) x /10i $eip
>
> I get this - which means it's not actually reading or displaying the memory
> properly, since those look to be what you would see if it wa
Hi Steve...
> Hi -
>
> I'm having a bit of trouble getting gdb to do what I was hoping it
> would with qemu. Following the instructions in the docs:
>
> #1) I launch qemu with -S -s flags ( since I want to trace the
> bootloader code )
> It says: Waiting gdb connection on port 1234 - which is corr
Hi -
I'm having a bit of trouble getting gdb to do what I was hoping it would
with qemu. Following the instructions in the docs:
#1) I launch qemu with -S -s flags ( since I want to trace the bootloader
code )
It says: Waiting gdb connection on port 1234 - which is correct, and it
opens the
