core dump

Asif Iqbal vadud3 at gmail.com
Thu Oct 1 18:12:30 CEST 2009


I had a core dump with bb on non-global solaris 10 zone on T1000
bash-3.00# gdb ~hobbit/client/bin/bb core
GNU gdb 6.6
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 "sparc-sun-solaris2.8"...
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libsocket.so.1...done.
Loaded symbols for /lib/libsocket.so.1
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libc.so.1...done.
Loaded symbols for /lib/libc.so.1
Reading symbols from /platform/sun4v/lib/libc_psr.so.1...done.
Loaded symbols for /platform/SUNW,Sun-Fire-T1000/lib/libc_psr.so.1
Reading symbols from /lib/ld.so.1...done.
Loaded symbols for /lib/ld.so.1
Core was generated by `/home/hobbit/client/bin/bb 0.0.0.0 @'.
Program terminated with signal 11, Segmentation fault.
#0  0xff109644 in doformat () from /lib/libc.so.1
(gdb) bt
#0  0xff109644 in doformat () from /lib/libc.so.1
#1  0xff10ac90 in strftime () from /lib/libc.so.1
#2  0x00013594 in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:47
#3  0x00013a28 in xmalloc (size=121384) at memory.c:121
#4  0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#5  0x00013a28 in xmalloc (size=121384) at memory.c:121
#6  0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#7  0x00013a28 in xmalloc (size=121384) at memory.c:121
#8  0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#9  0x00013a28 in xmalloc (size=121384) at memory.c:121
#10 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#11 0x00013a28 in xmalloc (size=121384) at memory.c:121
#12 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#13 0x00013a28 in xmalloc (size=121384) at memory.c:121
#14 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#15 0x00013a28 in xmalloc (size=121384) at memory.c:121
---Type <return> to continue, or q <return> to quit---
#16 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#17 0x00013a28 in xmalloc (size=121384) at memory.c:121
#18 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#19 0x00013a28 in xmalloc (size=121384) at memory.c:121
#20 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#21 0x00013a28 in xmalloc (size=121384) at memory.c:121
#22 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#23 0x00013a28 in xmalloc (size=121384) at memory.c:121
#24 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#25 0x00013a28 in xmalloc (size=121384) at memory.c:121
#26 0x0001362c in errprintf (fmt=0x1da28 "xmalloc: Out of memory!\n")
    at errormsg.c:61
#27 0x00013a28 in xmalloc (size=121384) at memory.c:121
#28 0x0001362c in errprintf (fmt=0x1da48 "xrealloc: Out of memory!\n")
    at errormsg.c:61
#29 0x00013a68 in xrealloc (ptr=0x0, size=195584) at memory.c:151
#30 0x00017d80 in strbuf_addtobuffer (buf=0x302a0,
    newtext=0x51cc0 ' ' <repeats 34 times>, "(sparc)
2.6.0,REV=10.0.3.2004.12.15---Type <return> to continue, or q <return> to
quit---
.20.59\n", newlen=76) at strfunc.c:109
#31 0x00012b44 in main (argc=3, argv=0xffbff51c) at bb.c:118
(gdb)


Let me know if I should have sent the backtrace directly to Henrik instead.

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20091001/1ab47f01/attachment.html>


More information about the Xymon mailing list