Date: Tue, 7 Mar 2000 18:22:04 -0600 (CST) From: Kevin Day <toasty@dragondata.com> To: hackers@freebsd.org Subject: SEGV in memInit Message-ID: <200003080022.SAA94121@celery.dragondata.com>
next in thread | raw e-mail | index | archive | help
We're having a problem where very very rarely we get a segfault on exec of
something, and I finally caught it:
# gdb menu
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd"...
(gdb) run
Starting program: /t/menu/menu
Program received signal SIGSEGV, Segmentation fault.
0x281c662d in ?? ()
(gdb) bt
#0 0x281c662d in ?? ()
#1 0x8075b1d in memLog (format=0x80970bb "Memory system started\n")
at mem.cpp:94
#2 0x8075dcc in memInit () at mem.cpp:186
#3 0x8075e23 in memAlloc (size=160, function=0x0, file=0x8097321 "new()",
line=0) at mem.cpp:208
#4 0x80764a6 in __builtin_new (size=160) at mem.cpp:503
#5 0x8077e27 in __builtin_vec_new ()
#6 0x281125cd in ?? ()
#7 0x28112109 in ?? ()
#8 0x280eaca4 in ?? ()
#9 0x280e9b91 in ?? ()
#10 0x2809a47c in ?? ()
#11 0x2809a328 in ?? ()
Any idea what causes this? I've got a core if necessary.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003080022.SAA94121>