[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mutt/libc? problems after recent sid upgrade



On Thu, Jan 09, 2003 at 03:34:32PM -0500, Bart Trojanowski wrote:
> OK, we need to find out what is calling the offending libc call.  Can
> you make it crash while running in gdb and brovide us with the backtrace
> (gdb command 'bt')?

On Thu, Jan 09, 2003 at 03:35:05PM -0500, H. S. Teoh wrote:
> This looks like a regex bug in libc. See #175163.

Yes, there seems to be an infinite recursion in re_comp(). When I just
kept Enter pressed in gdb, it kept displaying the same address at least
to #10000 (when I stopped).

This computer has the libc6 2.3.1-9 package installed.

Thanks for the help.


gdb mutt
GNU gdb 5.3-debian
Copyright 2002 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 "i386-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/mutt 
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(B)0[?1049h[?1h=(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
[?1049l
[?1l>(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x400d7bea in mallopt () from /lib/libc.so.6
(gdb) bt
#0  0x400d7bea in mallopt () from /lib/libc.so.6
#1  0x400d6fed in malloc () from /lib/libc.so.6
#2  0x4011c182 in re_exec () from /lib/libc.so.6
#3  0x4011c90b in re_exec () from /lib/libc.so.6
#4  0x40112638 in re_comp () from /lib/libc.so.6
#5  0x4011265f in re_comp () from /lib/libc.so.6
#6  0x4011265f in re_comp () from /lib/libc.so.6
#7  0x4011265f in re_comp () from /lib/libc.so.6
#8  0x4011265f in re_comp () from /lib/libc.so.6
#9  0x4011265f in re_comp () from /lib/libc.so.6
#10 0x4011265f in re_comp () from /lib/libc.so.6
#11 0x4011265f in re_comp () from /lib/libc.so.6
#12 0x4011265f in re_comp () from /lib/libc.so.6
#13 0x4011265f in re_comp () from /lib/libc.so.6
#14 0x4011265f in re_comp () from /lib/libc.so.6
#15 0x4011265f in re_comp () from /lib/libc.so.6
#16 0x4011265f in re_comp () from /lib/libc.so.6
#17 0x4011265f in re_comp () from /lib/libc.so.6
#18 0x4011265f in re_comp () from /lib/libc.so.6
#19 0x4011265f in re_comp () from /lib/libc.so.6
#20 0x4011265f in re_comp () from /lib/libc.so.6
#21 0x4011265f in re_comp () from /lib/libc.so.6
#22 0x4011265f in re_comp () from /lib/libc.so.6
#23 0x4011265f in re_comp () from /lib/libc.so.6
---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) quit
A debugging session is active.
Do you still want to close the debugger?(y or n) y
freefall ~ $ exit

-- 
Lee Bradshaw                 lee@sectionIV.com
Texas Instruments            bradshaw@ti.com
GnuPG D8C3BBD2  CC08 D690 0B70 3C70 351E  EB05 96A3 3789 D8C3 BBD2



Reply to: