Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] stack.c: move address printing into hook (fwd)
Date: Sun, 13 Jan 2002 12:20:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0201131219320.28257-100000@makita.cygnus.com> (raw)
In-Reply-To: <3C41B84E.6070405@cygnus.com>

On Sun, 13 Jan 2002, Andrew Cagney wrote:

> Yes ok.

Committed. Thanks.

> (This continues to work around the more fundamental problem of Insight
> not being able to ask GDB ``where are you'' and instead must still reap
> that info from the stop messages).

Yup. Still needing that patch for handle_inferior_event...

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

Keith



  reply	other threads:[~2002-01-13 20:20 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 [this message]
2002-01-13 12:40     ` 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=Pine.GSO.4.33.0201131219320.28257-100000@makita.cygnus.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@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