Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: ddaney@avtrex.com, gdb@sourceware.org
Subject: Re: [rfc/remote] Tell remote stubs which signals are boring
Date: Thu, 26 Oct 2006 07:02:00 -0000	[thread overview]
Message-ID: <E1GczGN-0006oc-Q7@fencepost.gnu.org> (raw)
In-Reply-To: <20061026014027.GA9023@nevyn.them.org> (message from Daniel 	Jacobowitz on Wed, 25 Oct 2006 21:40:27 -0400)

> Date: Wed, 25 Oct 2006 21:40:27 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sourceware.org
> > 
> > Does this mean that you have to issue a 'set remote pass-signals' 
> > command, or is it done automatically for 'handle noprint nostop pass' if 
> > the remote stub supports it?
> > 
> > Not being that familiar with the remote protocol, it is unclear to me.
> 
> It will just work.

Then this should be mentioned in the manual, both where the new packet
and command are described, and where the "handle" command is
described.


  reply	other threads:[~2006-10-26  7:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 21:24 Daniel Jacobowitz
2006-10-25 21:33 ` Mark Kettenis
2006-10-25 22:56 ` David Daney
2006-10-26  1:40   ` Daniel Jacobowitz
2006-10-26  7:02     ` Eli Zaretskii [this message]
2006-10-26  6:57 ` Eli Zaretskii
2006-10-26 12:18   ` Daniel Jacobowitz
2006-10-26 15:01     ` Eli Zaretskii
2006-10-26 15:10       ` Daniel Jacobowitz
2006-10-26 15:18         ` Eli Zaretskii
2006-10-26 15:22           ` Daniel Jacobowitz
2006-10-26 15:27     ` Mark Kettenis
2006-10-26 15:37       ` Daniel Jacobowitz
2006-10-26 17:54         ` Mark Kettenis
2006-10-26 21:11 ` Jim Blandy
2006-10-26 21:16   ` Daniel Jacobowitz
2006-10-26 21:28     ` Jim Blandy
2006-10-26 21:37       ` Daniel Jacobowitz

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=E1GczGN-0006oc-Q7@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=ddaney@avtrex.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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