From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] stack.c: move address printing into hook (fwd)
Date: Sun, 13 Jan 2002 12:40:00 -0000 [thread overview]
Message-ID: <3C41F09C.7040308@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0201131219320.28257-100000@makita.cygnus.com>
> Of course, if you just mention to me how you'd like it to be solved, I
> would be more than happy to try to implement something to your liking...
> ;-)
The theory is simple.
The code building the stop message should be separate to the code
determining why the target stopped. That way the CLI and the MI/Insight
can each separatly query for the stop reason.
This in turn means that, for Insight, your logic can read:
when (target stopped event)
get stop reason
process stop reason
I think I've now attempted this three times and three times it has
beaten me :-( The way GDB constructs its stop info is totally screwed up.
Andrew
prev parent reply other threads:[~2002-01-13 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 16:03 Keith Seitz
2002-01-13 8:39 ` Andrew Cagney
2002-01-13 12:20 ` Keith Seitz
2002-01-13 12:40 ` Andrew Cagney [this message]
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=3C41F09C.7040308@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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