public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: cancel: Re: [patch 5/9]#2 Move siginfo_fixup linux-nat -> inf-ptrace
Date: Tue, 31 Aug 2010 18:16:00 -0000	[thread overview]
Message-ID: <20100831181648.GC10352@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201008301144.o7UBiHr9023794@glazunov.sibelius.xs4all.nl>

Hi,

cancelling now this patch as being just a pre-requisite for:
	cancel: Re: [rfc 7/9]#2 Associate siginfo_t with any signal
	http://sourceware.org/ml/gdb-patches/2010-08/msg00545.html


On Mon, 30 Aug 2010 13:44:17 +0200, Mark Kettenis wrote:
>   but my gut feeling is that the siginfo
>   processing is (at least for now) a Linux-specific feature and
>   therefore belongs in linux-nat.c.

I see now that the siginfo corruption is more a bug in linux-nat.c only than
a general GDB bug.


> * The memcpy that's being done requires the size of "struct siginfo"
>   to be known.  I'm not sure all platforms that use ptrace(2) actually
>   have a "struct siginfo" (OpenBSD, HP-UX 10.20 and Linux have it).
>   I'm not sure <signal.h> is enough to actually make the definition
>   available (have some doubts here for HP-UX 10.20).

There was that HAVE_SIGINFO_T for it but it is offtopic now.


Thanks,
Jan

      reply	other threads:[~2010-08-31 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  7:13 Jan Kratochvil
2010-08-30 11:44 ` Mark Kettenis
2010-08-31 18:16   ` Jan Kratochvil [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=20100831181648.GC10352@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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).