Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Is stub support for the 's' packet optional or required?
Date: Tue, 18 Feb 2003 16:30:00 -0000	[thread overview]
Message-ID: <1030218162957.ZM3642@localhost.localdomain> (raw)
In-Reply-To: ac131313@redhat.com (Andrew Cagney) "Re: Is stub support for the 's' packet optional or required?" (Feb 17,  9:04pm)

On Feb 17,  9:04pm, Andrew Cagney wrote:

> If GDB implements software single step, then the `s' packet is never
> used.  Consequently, requiring the unconditional implementation of "s"
> makes little sense.

What about the situation where GDB implements software single step AND
the stub implements the 's' packet?  Shouldn't GDB at least attempt to
see if the stub supports the 's' packet before deciding to never send
it?

[For remote MIPS/Linux targets, I've found some cases where GDB's
implementation of software singlestep causes some undesirable behavior
when doing the 'stepi' operation through some code that's hit by a number
of threads.  Yet, when software single step is implemented in the debug
agent (and disabled in GDB), the debugging behavior is much more useful
(and sensible).]


Kevin


  reply	other threads:[~2003-02-18 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 23:50 Kevin Buettner
2003-02-18  2:39 ` Andrew Cagney
2003-02-18 16:30   ` Kevin Buettner [this message]
2003-02-18 16:51     ` Daniel Jacobowitz
2003-02-18 20:06       ` Kevin Buettner
2003-02-18 20:23         ` Daniel Jacobowitz
2003-02-18 20:42           ` Kevin Buettner
2003-02-18 21:03       ` Andrew Cagney
2003-02-18 21:43         ` Kevin Buettner
2003-02-18 23:43           ` 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=1030218162957.ZM3642@localhost.localdomain \
    --to=kevinb@redhat.com \
    --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