From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sources.redhat.com
Subject: Re: fullname descriptor with -break-list
Date: Mon, 07 Feb 2005 20:14:00 -0000 [thread overview]
Message-ID: <420787A3.2070605@gnu.org> (raw)
In-Reply-To: <20050207134829.GA21985@white>
>>-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"}
>
>
> O wow, it would be great to add this. I've been working on the MI
> testsuite lately, and after I'm done with that, I'll most likely end up
> wanting this exact feature. Otherwise, I'll have to call
> -file-list-exec-source-file every time instead.
>
>
>>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?
>
>
> I don't recall anything about this. Sorry.
The way that message is generated is a massive kludge - so the
underlying code could do with a cleanup - separate the code determining
why the process stopped from the code printing the stop reason.
Andrew
next prev parent reply other threads:[~2005-02-07 15:22 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
2005-02-07 14:54 ` Bob Rossi
2005-02-07 20:14 ` Andrew Cagney [this message]
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=420787A3.2070605@gnu.org \
--to=cagney@gnu.org \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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