Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: Re: [rfc][rft (procfs, nto-procfs)] Fix signal bypass heuristic with software single-step
Date: Tue, 22 Mar 2011 17:37:00 -0000	[thread overview]
Message-ID: <m3tyevrufm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201103182020.p2IKKnoF003371@d06av02.portsmouth.uk.ibm.com>	(Ulrich Weigand's message of "Fri, 18 Mar 2011 21:20:49 +0100 (CET)")

>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:

Ulrich> -/* post process changes to signal handling in the inferior.  */
Ulrich> +/* Set list of signals to be handled in the target.  */
 
Ulrich> -#define target_notice_signals(ptid) \
Ulrich> -     (*current_target.to_notice_signals) (ptid)
Ulrich> +extern void target_pass_signals (int nsig, unsigned char *pass_signals);

I would like it if there were more documentation about what this method
means and how it is used.  Actually, I suppose I would prefer it on the
field in struct target_ops, to be read by people porting gdb.

Tom


      parent reply	other threads:[~2011-03-22 16:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  1:54 Ulrich Weigand
2011-03-22 17:25 ` Pedro Alves
2011-03-24 16:39   ` Ulrich Weigand
2011-03-31 19:42   ` [rfc v2][rft " Ulrich Weigand
2011-04-04  9:47     ` Pedro Alves
2011-04-05 19:22       ` Ulrich Weigand
2011-04-05 19:33         ` Aleksandar Ristovski
2011-04-05 22:56           ` Ulrich Weigand
2011-04-06  1:37             ` Aleksandar Ristovski
2011-04-06 17:00               ` Ulrich Weigand
2011-04-26 17:34               ` Ulrich Weigand
2011-04-06  6:07         ` Joel Brobecker
2011-04-06 17:01           ` Ulrich Weigand
2011-04-27  1:12         ` Joel Brobecker
2011-04-27 13:31           ` Ulrich Weigand
2011-03-22 17:37 ` Tom Tromey [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=m3tyevrufm.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=uweigand@de.ibm.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