gdb/263: internal error when doing "info threads"

Daniel Jacobowitz drow@mvista.com
Tue Dec 18 19:18:00 GMT 2001


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

From: Daniel Jacobowitz <drow@mvista.com>
To: tabbott@systemsfusion.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/263: internal error when doing "info threads"
Date: Tue, 18 Dec 2001 22:09:17 -0500

 On Tue, Dec 18, 2001 at 09:36:46AM -0000, tabbott@systemsfusion.com wrote:
 > 
 > >Number:         263
 > >Category:       gdb
 > >Synopsis:       internal error when doing "info threads"
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Tue Dec 18 01:48:01 PST 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     tabbott@systemsfusion.com
 > >Release:        5.1
 > >Organization:
 > >Environment:
 > gdb 5.1 on Linux RH6.2, gcc 2.95.3 and kernel 2.4.12
 > >Description:
 > When doing "info threads" on a particular core file I get an internal error. Other core files do not give this problem.
 > 
 > (gdb) info threads
 > lin-lwp.c:1292: gdb-internal-error: lin_lwp_thread_alive: Assertion `is_lwp (ptid)' failed.
 > An internal GDB error was detected.  This may make further
 > debugging unreliable.  Continue this debugging session? (y or n) n
 > Create a core file containing the current state of GDB? (y or n) y
 > Aborted (core dumped)
 
 [Where'd you come up with multithreaded core files on Linux? :)]
 
 Please see the discussion on gdb-patches about this problem, for more
 information or my workaround.
 
 -- 
 Daniel Jacobowitz                           Carnegie Mellon University
 MontaVista Software                         Debian GNU/Linux Developer



More information about the Gdb-prs mailing list