public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/15103] disassemble file:function should work Date: Wed, 06 Feb 2013 18:29:00 -0000 [thread overview] Message-ID: <bug-15103-4717-ZLbyMgY3zD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15103-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15103 --- Comment #4 from Tom Tromey <tromey at redhat dot com> 2013-02-06 18:29:23 UTC --- (In reply to comment #2) > Re: disassemble takes expressions, not linespecs. > > That's not really my point though, is it. I didn't know. I thought it was an actual question. > 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? There's already an extension for this. Try: disassemble 'p-exp.y'::parse_number > But getting back to disassemble, > from a u/i perspective I can't rationalize the current behaviour. Linespecs might have been a better choice, but the choice has already been made. -- 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.
next prev parent reply other threads:[~2013-02-06 18:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-05 21:47 [Bug symtab/15103] New: " dje at google dot com 2013-02-06 12:18 ` [Bug symtab/15103] " tromey at redhat dot com 2013-02-06 18:19 ` dje at google dot com 2013-02-06 18:23 ` dje at google dot com 2013-02-06 18:29 ` tromey at redhat dot com [this message] 2013-02-06 19:16 ` dje at google dot com 2023-02-10 18:42 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15103-4717-ZLbyMgY3zD@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).