From: Daniel Jacobowitz <drow@false.org>
To: John Fodor <john_fodor@mac.com>
Cc: gdb@sourceware.org
Subject: Re: gdb and multi-threaded (NPTL) programs
Date: Fri, 24 Mar 2006 21:07:00 -0000 [thread overview]
Message-ID: <20060324204740.GA27767@nevyn.them.org> (raw)
In-Reply-To: <44245A19.8060808@mac.com>
On Fri, Mar 24, 2006 at 03:44:09PM -0500, John Fodor wrote:
> Sounds like a good idea. Let me know how it goes :)
Sorry, you're the one objecting to the current behavior :-)
I've done my share of fixing these bugs; I don't have time to try
another one.
> I wasn't referring to sem_wait specifically. I was thinking of any
> general syscall that will return EINTR after a SIGALARM.
That's receving a signal, not timing out. But anyway.
> >In practice this does not bother most programmers. If your application
> >uses signals, it often needs to do this anyway!
> >
>
> If you use signals you can set SA_RESTART for catchable signals.
That only works for restartable syscalls - sem_wait is not, in fact,
restartable, and I believe that restarting it after SA_RESTART would
violate the POSIX spec. Not 100% sure on that though.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-24 20:47 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 [this message]
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
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=20060324204740.GA27767@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=john_fodor@mac.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