This is the mail archive of the gdb-prs@sourceware.org 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]

[Bug symtab/15103] disassemble file:function should work


http://sourceware.org/bugzilla/show_bug.cgi?id=15103

--- Comment #2 from dje at google dot com 2013-02-06 18:19:18 UTC ---
Re: disassemble takes expressions, not linespecs.

That's not really my point though, is it.

Let's take a step back.
How do I explain to a user that while, yes, s/he can set a breakpoint on
p-exp.y:parse_number, s/he cannot disassemble it (in any easy way).
I could be missing something of course.

btw, somewhat related and somewhat tangential, I think we'll want to expand
expressions to take file names.
How do I (easily) print foo.c:baz instead of bar.c:baz from an arbitrary point
in the program?

"print foo.c:baz" is the obvious choice of course, but I if necessary (and
acceptable) I could see "print -f foo.c baz". It does preclude expressions
based on multiple files, but I can live with that.
[Some might want /X instead of -f, where X is some as yet unused display option
for print, but I'm not convinced it's better.]
[Again, this is all assuming "print foo.c:baz" can't work.
Plus, while linespecs don't always rquire filenames to be quoted, I could live
with "print 'foo.c':baz" too, if necessary.]

But getting back to disassemble,
from a u/i perspective I can't rationalize the current behaviour.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


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