Search the web
Sign In
New User? Sign Up
dmalloc · Debug Malloc Library (dmalloc) Group
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Want your group to be featured on the Yahoo! Groups website? Add a group photo to Flickr.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Thread nastiness?   Message List  
Reply | Forward Message #107 of 529 |
It's the monster stack trace from hell:

(gdb) r --sim
Starting program: /home/michael/src/HG2/run/hg2 --sim

Program received signal SIGSEGV, Segmentation fault.
0x4043880f in _IO_vfprintf (s=0x403d0860,
format=0x80a4887 "Executing log function\n", ap=0xbffff37c)
at vfprintf.c:242
vfprintf.c:242: No such file or directory.
Current language: auto; currently c
(gdb) where
#0 0x4043880f in _IO_vfprintf (s=0x403d0860,
format=0x80a4887 "Executing log function\n", ap=0xbffff37c)
at vfprintf.c:242
#1 0x40440720 in printf (format=0x80a4887 "Executing log function\n")
at printf.c:31
#2 0x8052587 in _dmalloc_environ_get (environ=0x80a3efd
"DMALLOC_OPTIONS",
addr_p=0x80c04d8, addr_count_p=0x80c04dc, debug_p=0x80c04e0,
interval_p=0x80c04e8, lock_on_p=0x80bfde0, logpath_p=0x80c04d4,
sfile_p=0x80bfdd4, sline_p=0x80bfdd8, scount_p=0x80bfddc) at
env.c:264
#3 0x8051542 in process_environ () at ./malloc.c:325
#4 0x80515de in dmalloc_startup () at ./malloc.c:397
#5 0x80513a2 in check_debug_vars (
file=0x403be021 "\203\020\211\211\006\213\203 wrote\022", line=0)
at ./malloc.c:238
#6 0x805170e in _loc_malloc (
file=0x403be021 "\203\020\211\211\006\213\203 about\022", line=0,
size=640,
func_id=10, alignment=0) at ./malloc.c:581
#7 0x80519a3 in malloc (size=640) at ./malloc.c:758
#8 0x403be021 in __default_alloc_template<true, 0>::_S_chunk_alloc (
__size=16, __nobjs=@0xbffff8a8)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_alloc.h:490
#9 0x403be17d in __default_alloc_template<true, 0>::_S_refill
(__n=16)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_alloc.h:531
#10 0x403bf56f in __default_alloc_template<true, 0>::allocate (__n=12)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_alloc.h:419
#11 0x403c7154 in simple_alloc<_List_node<NETFunc::Message *>,
__default_alloc_template<true, 0> >::allocate (__n=1)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_alloc.h:228
#12 0x403c4ca0 in _List_alloc_base<NETFunc::Message *,
allocator<NETFunc::Message *>, true>::_M_get_node (this=0x403d7480)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_list.h:168
#13 0x403c0c38 in _List_base<NETFunc::Message *,
allocator<NETFunc::Message *> >::_List_base (this=0x403d7480,
__a=@0xbffff9d8)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_list.h:187
#14 0x403c4d24 in list<NETFunc::Message *, allocator<NETFunc::Message
*> >::list (this=0x403d7480, __a=@0xbffff9d8)
at
/usr/local/gcc-2.95.2-4/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include\
/g++-3/stl_list.h:310
#15 0x403c0d18 in NETFunc::List<NETFunc::Message>::List
(this=0x403d7480)
at ../shell/netfunc/netfunc.h:212
#16 0x403a5b0b in NETFunc::Messages::Messages (this=0x403d7480)
at ../shell/netfunc/netfunc.cpp:345
#17 0x403b25e0 in __static_initialization_and_destruction_0
(__initialize_p=1,
__priority=65535) at ../shell/netfunc/netfunc.cpp:370
#18 0x403b2761 in global constructors keyed to
adialup_autodial_enabled ()
at ../shell/netfunc/netfunc.cpp:1977
#19 0x403bdaca in __do_global_ctors_aux ()
at ../../gcc-2.95.2/gcc/cp/tinfo2.cc:300
#20 0x4039721a in _init ()

Yes, I am linking with dmallocth.

[michael@namaste run]$ echo $DMALLOC_OPTIONS
debug=0x1df47deb,inter=1000,log=dmalloc.log

[michael@namaste HG2]$ rm -f hg2; make HG2_FLAGS='dmalloc' hg2 && cp
-f hg2 ./run/
/usr/local/gcc-2.95.2-4/bin/g++ -o hg2 stub/stub.o util/ref.o
generic/logging.o loki/libloki.o -L/usr/X11R6/lib -Lnetwork -lSDL
`glib-config --libs gthread` -ldl -lpthread -lX11 -lXext -lXxf86dga
-lXxf86vm -lGL -lz -lm -lnetwork -ldmallocth ./../loki_utils/libloki.a
./network/anet/linux86/lib/dp2d.a

We thought we had this fixed, but apparently not. Dmalloc is a *very*
valuable tool for us, so I was hoping someone might have some
suggestions as to why this is happenning. Our previous problem was
with thread nastiness, but to the best of my knowledge no threading is
involved whatsoever with this application. I have tried linking with
dmalloc instead of dmallocth to no avail.

Thoughts appreciated,

m.

--
Michael Vance "I wrote a song about dental floss,
Loki Entertainment Software but did anyone's teeth get cleaner?"
http://lokigames.com/~briareos/ - Frank Zappa, re: the PMRC



Wed Dec 8, 1999 11:49 pm

briareos@...
Send Email Send Email

Forward
Message #107 of 529 |
Expand Messages Author Sort by Date

It's the monster stack trace from hell: (gdb) r --sim Starting program: /home/michael/src/HG2/run/hg2 --sim Program received signal SIGSEGV, Segmentation...
Michael Vance
briareos@...
Send Email
Dec 8, 1999
11:46 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help