backtrace/2178: gdb crashes to thread_db_map_id2thr

Daniel Jacobowitz drow@false.org
Fri Sep 29 15:38:00 GMT 2006


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

From: Daniel Jacobowitz <drow@false.org>
To: seb128@ubuntu.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/2178: gdb crashes to thread_db_map_id2thr
Date: Fri, 29 Sep 2006 11:36:29 -0400

 On Fri, Sep 29, 2006 at 03:24:59PM -0000, seb128@ubuntu.com wrote:
 > "Program received signal SIGSEGV, Segmentation fault.
 > 0x000000000046410a in thread_db_map_id2thr (thread_info=0x0, fatal=0) at /tmp/gdb-6.5/gdb/linux-thread-db.c:318
 > 318       if (thread_info->private->th_valid)
 > (gdb) bt
 > #0  0x000000000046410a in thread_db_map_id2thr (thread_info=0x0, fatal=0) at /tmp/gdb-6.5/gdb/linux-thread-db.c:318
 > #1  0x0000000000466212 in thread_db_pid_to_str (ptid={pid = 8526, lwp = 8538, tid = 1124096336})
 >     at /tmp/gdb-6.5/gdb/linux-thread-db.c:1208
 
 Could you try CVS HEAD?  This particular crash will definitely be
 gone, since thread_db_map_id2thr is no longer called in most cases.
 
 > #9  0x0000000000449191 in error (string=0x695ac7 "%s.") at /tmp/gdb-6.5/gdb/utils.c:649
 > #10 0x000000000044982f in perror_with_name (string=0x6f1576 "ptrace") at /tmp/gdb-6.5/gdb/utils.c:865
 > #11 0x00000000005ada8d in inf_ptrace_resume (ptid={pid = 8526, lwp = 8538, tid = 0}, step=0, signal=TARGET_SIGNAL_0)
 >     at /tmp/gdb-6.5/gdb/inf-ptrace.c:343
 
 This may represent a different problem though.
 
 
 -- 
 Daniel Jacobowitz
 CodeSourcery



More information about the Gdb-prs mailing list