Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51856 - glibc/ntpl produces incoherent core dumps with abort()
Summary: glibc/ntpl produces incoherent core dumps with abort()
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-23 14:01 UTC by Daniel M. Albro
Modified: 2005-07-25 11:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel M. Albro 2004-05-23 14:01:21 UTC
Using glibc (sys-libs/glibc-2.3.3_pre20040420) with nptl enabled, core dumps
produced by abort() appear to be stripped of all useful information.  You
get something like this:

 gdb a.out core
GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library
 "/lib/libthread_db.so.1".

Core was generated by `./a.out'.
Program terminated with signal 6, Aborted.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0  0xffffe410 in ?? ()
(gdb) up
#1  0xbffff1cc in ?? ()
(gdb) up
#2  0x00000006 in ?? ()
(gdb) up
#3  0x00006008 in ?? ()
(gdb) up
#4  0x481233d1 in raise () from /lib/libc.so.6
(gdb) up
#5  0x48124e67 in abort () from /lib/libc.so.6
(gdb) up
#6  0xbffff1e0 in ?? ()
(gdb) up
#7  0x00000000 in ?? ()
(gdb) up
#8  0x00000020 in ?? ()
(gdb) up
#9  0x00000000 in ?? ()
(gdb) up


Reproducible: Always
Steps to Reproduce:
1. Emerge glibc with USE="ntpl" enabled
2. Create test.c: "#include <stdlib.h> void aborts() { abort(); } int main() { aborts(); return 1; }"
3. gcc -g test.c
4. ./a.out
5. gdb a.out core


Actual Results:  
Got the gdb session given above.

Expected Results:  
Should have shown a backtrace including "main" and "aborts".

Debian appears to have addressed this:
http://www.mail-archive.com/debian-glibc@lists.debian.org/msg09625.html
Comment 1 Caleb Tennis (RETIRED) gentoo-dev 2005-07-25 11:43:55 UTC
assuming fixed in latest versions.