From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: Andreas Schwab <schwab@suse.de>, John Fodor <john_fodor@mac.com>,
gdb@sourceware.org
Subject: Re: gdb and multi-threaded (NPTL) programs
Date: Tue, 28 Mar 2006 10:43:00 -0000 [thread overview]
Message-ID: <20060324212104.GA2812@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0603241315o22cd4757kb897425cd7606219@mail.gmail.com>
On Fri, Mar 24, 2006 at 01:15:26PM -0800, Jim Blandy wrote:
> So I'm agreeing with Daniel, I guess: it's a kernel bug. But it
> sounds to me like Daniel is saying that you need to find some change
> to the non-debugging behavior that would also fix the debugging
> behavior, which I don't agree with. In theory, you should change the
> debugging behavior and have no effect on the syscall's interface to
> the code that calls it.
That's not what I said at all. I said that you'd need to change
the kernel source code for the syscall to not return -EINTR, but
instead return some new code; I'm certainly not suggesting that the
new code ever be returned to userspace!
There is plenty of precedent for the construct I describe in the Linux
signal handling implementation.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-24 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 20:24 John Fodor
2006-03-24 20:27 ` Daniel Jacobowitz
2006-03-24 20:52 ` John Fodor
2006-03-24 21:07 ` Daniel Jacobowitz
2006-03-24 20:40 ` Andreas Schwab
2006-03-24 20:45 ` Eric Desjardins
2006-03-24 20:47 ` Andreas Schwab
2006-03-24 21:15 ` John Fodor
2006-03-24 21:21 ` Andreas Schwab
2006-03-28 9:33 ` Jim Blandy
2006-03-28 10:43 ` Daniel Jacobowitz [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=20060324212104.GA2812@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
--cc=john_fodor@mac.com \
--cc=schwab@suse.de \
/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