public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google 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 19:16:00 -0000	[thread overview]
Message-ID: <bug-15103-4717-e79nl9V33Z@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 #5 from dje at google dot com 2013-02-06 19:16:18 UTC ---
Blech.  Silly me for applying sane rules of design to gdb.

It's break foo.c:bar, but it's disassemble 'foo.c'::bar.

Except that disassemble 'foo.c'::bar doesn't work if the current language is
c++,
which is what my testcase was written in when I checked whether it worked
[filed as http://sourceware.org/bugzilla/show_bug.cgi?id=15109]

I consider this bug still open though. :-)
At least until a compelling reason is given for why neither of the following
can be done:
1) allow :: in linespecs
2) allow : in disassemble, et.al.

-- 
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.


  parent reply	other threads:[~2013-02-06 19:16 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
2013-02-06 19:16 ` dje at google dot com [this message]
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-e79nl9V33Z@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: link
Be 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).