From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Mosedale <dmose@mozilla.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: threads and target-function-calls
Date: Wed, 08 Jan 2003 03:27:00 -0000 [thread overview]
Message-ID: <20030108032712.GA616@nevyn.them.org> (raw)
In-Reply-To: <3E1B91B7.4010309@mozilla.org>
On Tue, Jan 07, 2003 at 06:49:27PM -0800, Dan Mosedale wrote:
> Daniel Jacobowitz wrote:
>
> >On Tue, Jan 07, 2003 at 05:00:25PM -0800, Michael Snyder wrote:
> >
> >
> >>Hey folks,
> >>
> >>Did you know that (at least on x86 linux), if you have a multi-thread
> >>program and you execute a target function call, all the threads get to
> >>run? Doesn't that seem like a bad thing? Wouldn't we really rather
> >>only run the thread that is executing the target function call?
> >>
> >>
> >
> >Eeeeek! I think I agree with you here; that's the logical behavior.
> >It never occured to me to try.
> >
> What happens if the target function wants to interact with another
> thread? e.g. wait on a mutex being held by another thread?
It'll deadlock; the user will Control-C; then he can either use
"return" to cancel the call, or free the mutex himself, or whatever.
Letting all threads just resume what they were doing doesn't seem to
make sense in general...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-08 3:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 1:00 Michael Snyder
2003-01-08 1:08 ` Daniel Jacobowitz
2003-01-08 2:49 ` Dan Mosedale
2003-01-08 3:27 ` Daniel Jacobowitz [this message]
2003-01-09 0:48 ` Michael Snyder
2003-01-09 1:51 ` Daniel Jacobowitz
2003-01-08 16:18 ` Andrew Cagney
2003-01-08 16:32 ` Daniel Jacobowitz
2003-01-09 0:47 ` Michael Snyder
2003-01-09 0:56 ` Michael Snyder
2003-01-09 1:05 ` Andrew Cagney
2003-01-15 19:39 ` Michael Snyder
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=20030108032712.GA616@nevyn.them.org \
--to=drow@mvista.com \
--cc=dmose@mozilla.org \
--cc=gdb-patches@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