Re: lin-thread cannot handle thread exit

[Michael Snyder <msnyder at cygnus dot com>]

Andrew Cagney wrote:
> 
> Michael Snyder wrote:
> >
> 
> > > All i ever debug on BeOS is multi-threaded apps.
> > > Almost anything you do involves threads.
> > > Open a window, you've started at least 2 threads.
> > > File selection boxes fill in a seperate thread, etc.
> > > So i constantly have threads coming and going, and doing things.
> > > The hardest part of the whole port of gdb is telling gdb what
> > > happened, and making gdb do the right thing.
> > > On BeOS, we don't even have processes, just teams and threads.
> > > Everything on BeOS works, except typing run and have it start (you
> > > have to run and continue) :P.
> > > I looked at thread_db over the weekend, in hopes of being able to redo
> > > the port and get it into GDB (it's badly needing a rewrite anyway),
> > > but it still looks like it has too many problems.
> >
> > What problems are you referring to?
> > Right now the only one I'm aware of is that it doesn't
> > detect thread exit.
> 
> Michael,
> 
> Did you get any further with this?  Did the problem exist in the old
> thread implementation for instance?
> 
>         Andrew

As far as I can tell, yes it did.
This is something that the thread_db implementation was
designed to handle -- I just didn't get around to it.
I hope to be able to fit it in "real soon now".