debugging assembler instructions

debugging assembler instructions

[Romain Guilleret]

		Hi,

I've written assembler code using __asm__. The code does not work as
expected and I would like to debug it.

Is it possible to do so using GDB ? Ideally, I would like gdb to stop
after every assembler instruction so that I can inspect memory or
registers to find what's wrong.

Is it possible to do so using GDB ?
If not, does anybody know another tool that could do it ?

I'm using GDB 5.2 on a Debian woody system.

TIA

	Romain Guilleret

Re: debugging assembler instructions

[Andreas Schwab]

Romain Guilleret <rguiller@free.fr> writes:

|> 		Hi,
|> 
|> I've written assembler code using __asm__. The code does not work as
|> expected and I would like to debug it.
|> 
|> Is it possible to do so using GDB ? Ideally, I would like gdb to stop
|> after every assembler instruction so that I can inspect memory or
|> registers to find what's wrong.
|> 
|> Is it possible to do so using GDB ?

What's wrong with stepi?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: debugging assembler instructions

[Romain Guilleret]

Well I didn't know stepi, and juste found it this morning.
And yes, it solves my problem.

Thanks anyway

Re: debugging assembler instructions

[Kris Warkentin]

You might want to try:

display /i $pc

and then use stepi.  This will show you the instruction you're on as you go.

cheers,

Kris

----- Original Message -----
From: "Romain Guilleret" <rguiller@free.fr>
To: <gdb@sources.redhat.com>
Sent: Wednesday, January 29, 2003 3:10 AM
Subject: debugging assembler instructions


> Hi,
>
> I've written assembler code using __asm__. The code does not work as
> expected and I would like to debug it.
>
> Is it possible to do so using GDB ? Ideally, I would like gdb to stop
> after every assembler instruction so that I can inspect memory or
> registers to find what's wrong.
>
> Is it possible to do so using GDB ?
> If not, does anybody know another tool that could do it ?
>
> I'm using GDB 5.2 on a Debian woody system.
>
> TIA
>
> Romain Guilleret
>