This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: What about add a interface to output the assembly codes follow inferior execution

On Wed, Mar 4, 2009 at 2:14 PM, Eli Zaretskii <> wrote:
>> Date: Wed, 4 Mar 2009 13:25:05 -0800
>> From: Doug Evans <>
>> Cc:, Daniel Jacobowitz <>,         Eli Zaretskii <>,
>> Ya, extending the disassemble command makes sense to me.
> I don't see how it can make sense that the same command does both
> one-time disassembly and disassemble the next source line each time
> GDB stops.  It's like "print" and "display" -- it's not an accident we
> have 2 different commands there.

I was not suggesting extending the disassemble command to handle the
specifying of source lines as a way to address the issue being
addressed by "set disassemble-next-line|show-opcodes foo".  [One could
use the stop hook, but that gets tricky if one wants to start doing
multiple things in the stop hook.]  I was merely saying that extending
the disassemble command to handle source lines is A Good Thing.

> If anything, extending "display" with yet another format specifier, or
> maybe a qualifier for /i, would make much more sense to me.

That would be another way to go instead of
disassemble-next-line|show-opcodes, yes.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]