From: Paul Hilfinger <hilfingr@gnat.com>
To: drow@false.org
Cc: gdb@sources.redhat.com
Subject: Re: GDB interaction with sigwait under Redhat 9.0
Date: Thu, 13 May 2004 09:33:00 -0000 [thread overview]
Message-ID: <20040513093318.C13DDF2A64@nile.gnat.com> (raw)
In-Reply-To: <20040512135530.GA25764@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 12 May 2004 09:55:30 -0400)
> On Wed, May 12, 2004 at 04:33:48AM -0400, Paul Hilfinger wrote:
> >
> > I recently submitted PR threads/1641 concerning a problem we seem to
> > be having with Redhat 9.0 (Linux ... 2.4.21-9.ELsmp #1 SMP Thu Jan 8
> > 17:08:56 EST 2004 i686 i686 i386 GNU/Linux). It appears that on that
> > system, there is a new, malign interaction of sigwait in the inferior
> > with ptrace. First, GDB (head version from about mid-April), no
> > longer sees signals sent to an inferior that is waiting on sigwait. Second,
> > GDB's manipulation with the inferior causes sigwaits (at least on
> > pthreaded programs) to continue with a non-zero status code (EINTR to
> > be precise). Does anyone know anything about this rather drastic change
> > in sigwait's behavior? I intend to submit a GNU/Linux bug report, unless
> > someone knows a good reason for this new (apparently undocumented) spec.
>
> However, you never
> said what version of the Linux kernel you were using - it does not look
> like 2.6 can produce this result. But then I don't see how an
> unmodified 2.4 can either.
Sorry; I thought the 2.4.21-9.ELsmp part of the uname -a line was
sufficient. In fact, not being a kernel hacker myself, I'm not sure what
information you're looking for here.
Paul Hilfinger
next prev parent reply other threads:[~2004-05-13 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 8:33 Paul Hilfinger
2004-05-12 13:55 ` Daniel Jacobowitz
2004-05-13 9:33 ` Paul Hilfinger [this message]
2004-05-13 13:30 ` Daniel Jacobowitz
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=20040513093318.C13DDF2A64@nile.gnat.com \
--to=hilfingr@gnat.com \
--cc=drow@false.org \
--cc=gdb@sources.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