From: Jeff Dike <jdike@karaya.com>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <dan@debian.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Signal/gdb oddity in 2.5.61
Date: Sun, 16 Feb 2003 21:34:23 -0500 [thread overview]
Message-ID: <200302170234.VAA03818@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sun, 16 Feb 2003 17:00:36 PST." <200302170100.h1H10aQ28610@magilla.sf.frob.com>
roland@redhat.com said:
> Anyone who wants to use an old gdb with a new kernel can use "handle
> SIGSTOP nopass". Is that a real imposition? Anyway, aside from the
> test suite, it only affects gdb users in a way that may confuse them
> for a few seconds but doesn't prevent them from debugging normally.
It may also affect UML, since it has come to know exactly what to expect
from a ptraced process. So, when you have the semantics nailed down and
implemented, can you see if UML still runs?
Not that it's a showstopper if it doesn't, but I'd like to know so I can
fiddle UML so that it continues to run.
Jeff
next prev parent reply other threads:[~2003-02-17 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302161117370.2874-100000@home.transmeta.com>
2003-02-16 22:28 ` Signal/gdb oddity in 2.5.61 Roland McGrath
2003-02-16 23:27 ` Daniel Jacobowitz
2003-02-16 23:44 ` Linus Torvalds
2003-02-17 1:00 ` Roland McGrath
2003-02-17 2:34 ` Jeff Dike [this message]
2003-02-17 3:02 ` Daniel Jacobowitz
2003-02-16 19:15 Russell King
2003-02-16 22:10 ` Daniel Jacobowitz
2003-02-16 22:14 ` Russell King
2003-02-16 22:21 ` Daniel Jacobowitz
2003-02-16 22:28 ` Russell King
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=200302170234.VAA03818@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=dan@debian.org \
--cc=roland@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