This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: lin-thread cannot handle thread exit
- To: dan at cgsoftware dot com
- Subject: Re: lin-thread cannot handle thread exit
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Thu, 09 Mar 2000 10:31:23 -0800
- CC: Mark Kettenis <kettenis at wins dot uva dot nl>, gdb at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <200003031635.e23GZwi00372@delius.kettenis.local> <38C59074.2D7C@cygnus.com> <u2ihhvav.fsf@dan.resnet.rochester.edu>
Daniel Berlin wrote:
>
> >
> > Hi Mark,
> >
> > The lin-thread / thread_db module was completed under time
> > pressure and took much longer to get working than expected;
> > plus of course it is a brand new native thread "port"
> > (although I had access to Eric Paire's work as an example).
> > So no, it isn't formally regarded as a "work in progress",
> > except in the sense that GDB itself is a work in progress,
> > but it isn't exactly mature code either.
> >
> > I appreciate your helping to find problems with it, and
> > I'd like to know what else in the code you regard as a
> > "loose end". One of my problems is that I'm not really
> > an experienced writer of multi-threaded apps -- I'm just
> > the person on the GDB team with the most experience with
> > GDB multi-thread debugging.
>
> 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.
> I'm more than willing to help with thread_db in any way i can to
> get it to work better.
> Like i said, all i ever work with is multi-threaded programs.
> My main C++ project is a development environment where almost
> everything is plugins, addons, and threads. At any given point in time
> there are about 16-20 threads going.
>
> >
> > Thanks,
> > Michael