This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: threads and target-function-calls

On Wed, Jan 08, 2003 at 04:48:35PM -0800, Michael Snyder 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.
> I just happened to have "debug lin-lwp" turned on.
> Perhaps we need to think about what "target function call"
> actually means in the presence of threads that can interact
> with each other.

Yeah.  My biggest concern is an interface one.  What the heck _should_
happen?  And how do we present it to the user?

[On an interesting side note, another debugger developer mentioned to
me that their product supports conditional breakpoints by inserting
code into the inferior.  That'd be nice to do some day... but we don't
really have the architecture for it right now...]

Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]