public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cagney@redhat.com, sid@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: sid debugger interface extension: step out-of-range packet support
Date: Fri, 22 Feb 2002 17:08:00 -0000	[thread overview]
Message-ID: <3C76E982.972553B6@redhat.com> (raw)
In-Reply-To: <o5y9hxfm9x.fsf@toenail.toronto.redhat.com>

"Frank Ch. Eigler" wrote:
> 
> cagney wrote:
> 
> > [...]
> > > A small amount of new code in sid/include and sid/component/gdb
> > > now allows gdb's "step out-of-range" packet ('e'/'E') to work with
> > > all sid-based simulator targets.  [...]
> >
> > [...]  I wouldn't rely to much on that current packet and/or
> > implementation.  A number of issues with it have been pointed out
> > with it.  Suggest looking through the archives.
> 
> I did.  Are you referring to a thread other than this one:
> <http://sources.redhat.com/ml/gdb/2001-02/msg00054.html> ?  I must
> admit I don't see the severity of that problem -- it sounds like the
> user experience may be a little jarring with multithreaded apps, but
> not inconsistent or lossy.

If the 'e' packet is going to change gdb's behavior while debugging
threads, this needs to be discussed and considered.  It may amount to
a bug in the specification of the 'e' packet.

And in fact, given the behavior that you describe in your first message, 
the 'e' packet _is_ going to change gdb's behavior while debugging
threads.

  parent reply	other threads:[~2002-02-23  1:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 14:14 Frank Ch. Eigler
2002-02-12 22:10 ` Andrew Cagney
2002-02-13  7:13   ` Frank Ch. Eigler
2002-02-13 12:52     ` Andrew Cagney
2002-02-22 17:08     ` Michael Snyder [this message]
2002-02-22 17:05 ` Michael Snyder
2002-02-22 19:28   ` Frank Ch. Eigler

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=3C76E982.972553B6@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).