Strange crash in glibc

Steve smorrey at gmail.com
Sat Mar 25 13:05:04 MST 2006


Hmm valgrind segfaults?


ashtara at SP4171a ~/mmorpg/example $ valgrind ./torqueDemod.bin
-dedicated -mission starter.rpg/data/missions/emerald.mis
==8858== Memcheck, a memory error detector for x86-linux.
==8858== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==8858== Using valgrind-2.4.0, a program supervision framework for x86-linux.
==8858== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==8858== For more details, rerun with: -v
==8858==
--8858-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--8858-- si_code=1 Fault EIP: 0xB00A7DFA (); Faulting address: 0x10
--8858--   esp=0xB0678E10


valgrind: the `impossible' happened:
   Killed by fatal signal
Basic block ctr is approximately 890621
==8858==    at 0xB00A7DFA: (within /usr/lib/valgrind/stage2)
==8858==    by 0xB0070243: vgPlain_client_syscall (in /usr/lib/valgrind/stage2)
==8858==    by 0xB001A559: (within /usr/lib/valgrind/stage2)
==8858==    by 0xB001AB9C: vgPlain_scheduler (in /usr/lib/valgrind/stage2)
==8858==    by 0xB00AA084: vgArch_thread_wrapper (in /usr/lib/valgrind/stage2)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==8858==    at 0x1BC2095C: clone (in /lib/libc-2.3.5.so)
==8858==    by 0x1B9B1549: pthread_create@@GLIBC_2.1 (in
/lib/libpthread-0.10.so)
==8858==    by 0x8314E9B: NetAsync::startAsync() (in
/home/ashtara/mmorpg/example/torqueDemod.bin)
==8858==    by 0x1BB8156C: __libc_start_main (in /lib/libc-2.3.5.so)
==8858==    by 0x804BB20: (within /home/ashtara/mmorpg/example/torqueDemod.bin)

Thread 2: status = VgTs_Init
==8858==    at 0x1BC2095C: clone (in /lib/libc-2.3.5.so)


Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.

If that doesn't help, please report this bug to: valgrind.kde.org

In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using.  Thanks.


Any other ideas?

On 3/25/06, Michael Torrie <torriem at chem.byu.edu> wrote:
> On Sat, 2006-03-25 at 12:38 -0700, Steve wrote:
> > I'm just looking for troubleshooting ideas, like where I might want to
> > start looking the code base is over 50 MBs of C++ and I'm only now
> > just familiarizing myself.
> > Sadly since it is a closed source app I can't use the many eyes
> > approach, but I'm hoping there is a clue somewhere that can let me
> > know where the memory is getting corrupted.
>
> Probably you'll want to run valgrind.  Valgrind can detect these types
> of double-free situations (very common errors in C and C++).
>
> Michael
>
>
> >
> > Any tips, tricks, ideas, thoughts etc would be greatly appreciated.
> >
> > /*
> > PLUG: http://plug.org, #utah on irc.freenode.net
> > Unsubscribe: http://plug.org/mailman/options/plug
> > Don't fear the penguin.
> > */
> >
>
> /*
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
> */
>



More information about the PLUG mailing list