From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: fullname descriptor with -break-list
Date: Mon, 07 Feb 2005 02:49:00 -0000 [thread overview]
Message-ID: <16902.45534.858929.941689@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050206210637.GB19609@white>
> > Would such a patch be acceptable?
>
> I believe it would be, when I added the -file-list commands, I was asked
> to add the information to the breakpoints and to the stack command.
>
> I didn't do it simply for time reasons. You can use the
> symtab_to_fullname or psymtab_to_fullname functions to get the data you
> need.
>
> In the long run, it would probably be usefull to output the fullname
> everywhere that "file" is used.
For the moment, I will start GDB with annotations and convert as many of the
CLI commands to MI as I can. I already use variable objects and I will add to
this. I don't currently need the fullname in the stack output because it
always gets printed for the current frame by annotations. Eventually I will
need to get this information from MI output. I notice, however, that, in MI,
the fullname *doesn't* get printed when execution stops:
-exec-run
^running
(gdb)
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x080486e2",func="myprint",args=[{name="i",value="0"},{name="j",value="0"}],file="myprint.c",line="5"}
I seem to recall there was some discussion about this earlier but I didn't
follow the thread closely. Can somebody please tell me what the outcome was?
Nick
next prev parent reply other threads:[~2005-02-07 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 23:18 Nick Roberts
2005-02-07 0:17 ` Bob Rossi
2005-02-07 2:49 ` Nick Roberts [this message]
2005-02-07 14:54 ` Bob Rossi
2005-02-07 20:14 ` Andrew Cagney
2005-02-08 1:54 ` Event notification in MI (was Re: fullname descriptor with -break-list) Nick Roberts
2005-03-04 7:24 ` fullname descriptor with -break-list Nick Roberts
2005-03-04 11:23 ` Bob Rossi
2005-02-07 15:22 ` Andrew Cagney
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=16902.45534.858929.941689@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
/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