Re: symtab/1255: [regression] bad backtrace for libc function 'sleep'

[Daniel Jacobowitz <drow at mvista dot com>]

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

From: Daniel Jacobowitz <drow@mvista.com>
To: mec@shout.net
Cc: gdb-gnats@sources.redhat.com
Subject: Re: symtab/1255: [regression] bad backtrace for libc function 'sleep'
Date: Fri, 1 Aug 2003 21:21:07 -0400

 On Tue, Jun 24, 2003 at 03:51:06PM -0000, mec@shout.net wrote:
 > 
 > >Number:         1255
 > >Category:       symtab
 > >Synopsis:       [regression] bad backtrace for libc function 'sleep'
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          change-request
 > >Submitter-Id:   net
 > >Arrival-Date:   Tue Jun 24 16:28:00 UTC 2003
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     mec@shout.net
 > >Release:        gdb HEAD 2003-05-30 20:00:00 UTC
 > >Organization:
 > >Environment:
 > target=native
 > host=i686-pc-linux-gnu
 > osversion=red-hat-8.0
 > gdb=HEAD%20030621
 > gcc=3.3
 > binutils=2.14
 > glibc=2.2.93-5-rh
 > gformat=dwarf-2
 > glevel=2
 > >Description:
 > I put a breakpoint deep inside a libc function, hit the breakpoint, and take a backtrace.  The backtrace craps out when it gets to the 'sleep' function in libc.
 > 
 > This is important, especially in a multi-threaded program.  A multi-threaded program is likely to have many threads that are sleeping or blocked.  This bug ruins the backtrace for such a thread.
 > 
 > This happened between gdb HEAD 2003-05-30 19:00:00 UTC and gdb HEAD 2003-05-30 20:00:00 UTC, this patch:
 
 I believe this is the same issue as 1253.  Again, it appears to be
 local to your glibc.  I can't reproduce it here on the 6.0 branch.
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer