Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, mark.kettenis@xs4all.nl
Subject: Re: [patch] Fix Linux attach to signalled/stopped processes
Date: Sat, 30 Jun 2007 11:57:00 -0000	[thread overview]
Message-ID: <uir95mzsu.fsf@gnu.org> (raw)
In-Reply-To: <20070630101854.GA29173@host0.dyn.jankratochvil.net> (message 	from Jan Kratochvil on Sat, 30 Jun 2007 12:18:54 +0200)

> Date: Sat, 30 Jun 2007 12:18:54 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>
> 
> On Wed, 27 Jun 2007 08:52:03 +0200, Jan Kratochvil wrote:
> ...
> > OK, going to move it to linux-nat.c.
> 
> Done; various parts changed.
> 
> 
> There is one ugly workaround part (described in the comments in the patch).
> Testcase for this workaround is also attached, it appears as (another) Linux
> kernel ptrace(2) bug to me.  Is it worth workarounding it?  IMO not worth
> fixing as it is a corner case and UTRACE is going to provide alternative API.
> 
> Tested on x86_64, on upstream 2.6.22-rc4-git7 and Red Hat kernel-2.6.9-55.EL.

Will this cause any user-visible changes in behavior?  If so, I think
we should reflect it in NEWS at the very least.

Thanks.


  reply	other threads:[~2007-06-30 11:45 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 14:34 Jan Kratochvil
2007-06-11 13:44 ` Jan Kratochvil
2007-06-15 18:02 ` Mark Kettenis
2007-06-26 22:40   ` Jan Kratochvil
2007-06-27  0:13     ` Mark Kettenis
2007-06-27 11:59       ` Jan Kratochvil
2007-06-27 18:30         ` Mark Kettenis
2007-06-30 11:45         ` Jan Kratochvil
2007-06-30 11:57           ` Eli Zaretskii [this message]
2007-06-30 17:15             ` Jan Kratochvil
2007-06-30 18:52               ` Eli Zaretskii
     [not found]               ` <200706301852.l5UIq8ek010536@brahms.sibelius.xs4all.nl>
2007-07-01  3:17                 ` Eli Zaretskii
2007-07-01  9:34                   ` Mark Kettenis
2007-07-01 10:03                     ` Jan Kratochvil
2008-03-31 22:07 Doug Evans
2008-04-02  0:01 ` Jan Kratochvil
2008-04-02  0:07   ` Roland McGrath
2008-04-10 15:30     ` Daniel Jacobowitz
2008-04-10 15:37       ` Jan Kratochvil
2008-04-10 15:49         ` Daniel Jacobowitz
2008-04-10 16:00           ` Jan Kratochvil
2008-04-10 19:59             ` Daniel Jacobowitz
2008-04-10 15:39   ` Daniel Jacobowitz
2008-04-10 16:00     ` Jan Kratochvil
2008-04-10 19:48       ` Daniel Jacobowitz
2008-04-11  8:46       ` Roland McGrath
2008-04-11 17:46         ` Jan Kratochvil
2008-04-11 19:01           ` Daniel Jacobowitz
2008-04-12  7:58           ` Roland McGrath
2008-04-14 15:09             ` Daniel Jacobowitz
2008-04-14 15:31               ` Daniel Jacobowitz
2008-04-15 22:14                 ` Jan Kratochvil
2008-05-01 18:50                   ` Daniel Jacobowitz
2008-07-05  8:48                     ` Jan Kratochvil
2008-07-05 13:48                       ` Daniel Jacobowitz
2008-09-24 12:46                 ` Andreas Schwab
2008-09-26  3:52                   ` Jan Kratochvil
2008-09-26 13:00                     ` Daniel Jacobowitz
2008-09-28 11:43                       ` Jan Kratochvil
2008-09-28 14:58                         ` Daniel Jacobowitz
2008-04-15  8:14               ` Roland McGrath
2008-04-15 13:02                 ` Daniel Jacobowitz
2008-04-16  7:01                   ` Roland McGrath
2008-04-11 22:20         ` Daniel Jacobowitz
2008-04-11 22:21           ` Pedro Alves
2008-04-11 22:25             ` Daniel Jacobowitz
2008-04-12  0:02               ` Pedro Alves
2008-04-12  0:19                 ` Pedro Alves
2008-04-13  9:35                   ` Pedro Alves
2008-04-13 13:40                     ` Pedro Alves
2008-04-12 16:38           ` Roland McGrath
2008-04-12 16:43           ` Eli Zaretskii

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=uir95mzsu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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