RE: toolchain/34194: gdb "info threads" does not work

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR toolchain/34194; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: <Paul_Koning%Dell.com@localhost>, <gnats-bugs%NetBSD.org@localhost>, 
<skrll%NetBSD.org@localhost>, 
        <gnats-admin%netbsd.org@localhost>, <netbsd-bugs%netbsd.org@localhost>, 
        <martin%aprisoft.de@localhost>
Cc: 
Subject: RE: toolchain/34194: gdb "info threads" does not work
Date: Fri, 9 Dec 2011 21:48:59 -0500

 On Dec 9, 11:02am, Paul_Koning%Dell.com@localhost 
(<Paul_Koning%Dell.com@localhost>) wrote:
 -- Subject: RE: toolchain/34194: gdb "info threads" does not work
 
 | > On Fri, Dec 09, 2011 at 05:34:37PM +0200, Andreas Gustafsson wrote:
 | > > The gdb "info threads" command is still broken as of today's -current  =
 | > (tested on i386).
 | > >
 | > > It would be really helpful if this and the other multithreading-related=
 |   > gdb bugs could be fixed, because all the currently failing ATF tests on=
 |   > the TNF test system are in rump-based tests which involve multithreaded=
 |   > processes and therefore can't easily be debugged using gdb as it stands=
 | .
 | >=20
 | > They can if you can get a core -- it works on cores.  Or did last week  w=
 | hen I was looking at, I think, the same problem you're looking at.
 | >=20
 | > Thor
 | =20
 | I need to get my live thread debug support cleaned up and submitted...  It'=
 | s been stuck behind priority interrupts for too long.
 
 Have you tried gdb recently? What in the threaded support does not work
 right now?
 
 christos