Bug#414513: marked as done (segment fault bug caused by libc6_2.3.6.ds1-13_i386)
Your message dated Mon, 12 Mar 2007 11:00:36 +0100
with message-id <45F524C4.5000600@aurel32.net>
and subject line Bug#414513: segment fault bug caused by libc6_2.3.6.ds1-13_i386
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
package: libc6
version: 2.3.6.ds1-13
when I ran 'sdcv'(a dictionary debian package), segment fault
occured. This bug is belonging to libc6, because yesterday my
laptop failed to resume to x-windows from the RAM-sleep(I use
suspend2 and hibernate script), and the error message points to
libc.so.6.
Today I downgrade libc6 to 2.3.6.ds1-11, sdcv works fine as
before. Note that both 2.3.6.ds1-12 and 2.3.6.ds1-13 do not work.
when I used 'gdb sdcv' with libc6 version 2.3.6.ds1-13, the
following debug message was obtained, please notice the last
several lines,
/***********the output of gdb**********************************/
GNU gdb 6.4.90-debian
Copyright (C) 2006 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 "i486-linux-gnu"...(no debugging
symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) r
Starting program: /usr/bin/sdcv
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211992384 (LWP 3083)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211992384 (LWP 3083)]
0xb7cf4833 in strlen () from /lib/tls/libc.so.6
(gdb) quit
/***********the end of output of gdb**************************/
I am using Debian GNU/Linux testing, kernel 2.6.18-4-686.
best regards,
F.Y.
--- End Message ---
--- Begin Message ---
Ye Fei a écrit :
> package: libc6
> version: 2.3.6.ds1-13
>
> when I ran 'sdcv'(a dictionary debian package), segment fault
> occured. This bug is belonging to libc6, because yesterday my
> laptop failed to resume to x-windows from the RAM-sleep(I use
> suspend2 and hibernate script), and the error message points to
> libc.so.6.
>
> Today I downgrade libc6 to 2.3.6.ds1-11, sdcv works fine as
> before. Note that both 2.3.6.ds1-12 and 2.3.6.ds1-13 do not work.
>
> when I used 'gdb sdcv' with libc6 version 2.3.6.ds1-13, the
> following debug message was obtained, please notice the last
> several lines,
> /***********the output of gdb**********************************/
> GNU gdb 6.4.90-debian
> Copyright (C) 2006 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 "i486-linux-gnu"...(no debugging
> symbols found)
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
>
> (gdb) r
> Starting program: /usr/bin/sdcv
> Failed to read a valid object file image from memory.
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1211992384 (LWP 3083)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1211992384 (LWP 3083)]
> 0xb7cf4833 in strlen () from /lib/tls/libc.so.6
Your program called strlen with an invalid pointer. There is no bug in
the glibc. Closing the bug.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: