Re: how to proceed when faced with malloc error

This generally happens when memory errors in the application under test
(here, "btserver") are so bad they wind up trashing Valgrind's storage
too.  If Valgrind has reported memory errors prior to this point, try
fixing them first.

J

> --19817-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - 
> exiting
> --19817-- si_code=128;  Faulting address: 0x0;  sp: 0x100993be30
> 
> valgrind: the 'impossible' happened:
>     Killed by fatal signal
> 
> host stacktrace:
> ==19817==    at 0x580492FF: get_bszB_as_is (m_mallocfree.c:302)
> ==19817==    by 0x580492FF: get_bszB (m_mallocfree.c:314)
> ==19817==    by 0x580492FF: vgPlain_arena_malloc (m_mallocfree.c:1819)
> ==19817==    by 0x58004D74: vgMemCheck_new_block (mc_malloc_wrappers.c:370)
> ==19817==    by 0x58004F99: vgMemCheck___builtin_new (mc_malloc_wrappers.c:415)
> ==19817==    by 0x58093FD5: do_client_request (scheduler.c:1979)
> ==19817==    by 0x58093FD5: vgPlain_scheduler (scheduler.c:1542)
> ==19817==    by 0x580DA8DA: thread_wrapper (syswrap-linux.c:102)
> ==19817==    by 0x580DA8DA: run_a_thread_NORETURN (syswrap-linux.c:155)
> 
> sched status:
>    running_tid=1
> 
> Thread 1: status = VgTs_Runnable (lwpid 19817)
> ==19817==    at 0x4841EF1: operator new(unsigned long) (vg_replace_malloc.c:472)
> ==19817==    by 0x60FFB3: Card::checkNewPort(LFInfo&, String const&, char 
> const*, bool, char const*, bool&, bool&, unsigned int) (Card.cc:7510)
> ==19817==    by 0x611337: Card::discoverDevices(LFInfo&, char const*, bool) 
> (Card.cc:8205)
> ==19817==    by 0x84815E: btserver_main(int, char**) (main.cc:1034)
> ==19817==    by 0x844F64: main (main.cc:157)
> client stack range: [0x1FFEFEA000 0x1FFF000FFF] client SP: 0x1FFEFFDB30
> valgrind stack range: [0x100983C000 0x100993BFFF] top usage: 13936 of 1048576



_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users