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] New: disassemble file:function should work
Date: Tue, 05 Feb 2013 21:47:00 -0000	[thread overview]
Message-ID: <bug-15103-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 15103
           Summary: disassemble file:function should work
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: symtab
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com
    Classification: Unclassified


bash$ gdb gdb
(gdb) b parse_number
Breakpoint 3 at 0x53793e: parse_number. (7 locations)
(top-gdb) i b
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000006edb0c in internal_error
                                                   at ../../src/gdb/utils.c:956
2       breakpoint     keep y   0x00000000004ed3e8 in info_command
                                                   at
../../src/gdb/cli/cli-cmds.c:221
        silent
        return
3       breakpoint     keep y   <MULTIPLE>
3.1                         y     0x000000000053793e in parse_number
                                                   at
../../src/gdb/cp-name-parser.y:1360
3.2                         y     0x000000000054c986 in parse_number
                                                   at ../../src/gdb/p-exp.y:861
3.3                         y     0x0000000000549dd8 in parse_number
                                                   at
../../src/gdb/m2-exp.y:665
3.4                         y     0x00000000005469cc in parse_number
                                                   at
../../src/gdb/go-exp.y:711
3.5                         y     0x00000000005442bc in parse_number
                                                   at ../../src/gdb/f-exp.y:674
3.6                         y     0x00000000005414a8 in parse_number
                                                   at
../../src/gdb/jv-exp.y:701
3.7                         y     0x0000000000531185 in parse_number
                                                   at
../../src/gdb/c-exp.y:1654
(top-gdb) disas p-exp.y:parse_number
No symbol "p" in current context.
(top-gdb) b p-exp.y:parse_number
Note: breakpoint 3 also set at pc 0x54c986.
Breakpoint 4 at 0x54c986: file ../../src/gdb/p-exp.y, line 861.
(top-gdb) 

If "b p-exp.y:parse_number" works,
why doesn't "disas p-exp.y:parse_number" ?

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


             reply	other threads:[~2013-02-05 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 21:47 dje at google dot com [this message]
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
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@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).