This is the mail archive of the
mailing list for the GDB project.
Re: threads and target-function-calls
- From: Michael Snyder <msnyder at redhat dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 08 Jan 2003 16:47:38 -0800
- Subject: Re: threads and target-function-calls
- Organization: Red Hat, Inc.
- References: <3E1B7829.6B6E8BAF@redhat.com> <3E1C4F29.email@example.com>
Andrew Cagney 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?
> Ha! That's just the start. Doing nested inferior function calls on
> alternative threads scrables the dummy frame cache:
But... that's just sick. ;-(
Wait -- you can't do that. It isn't meaningful to change threads
and then continue/whatever. It assumes gdb has more control over
scheduling than it actually has.