> valgrind: the 'impossible' happened:
> Killed by fatal signal
> ==31001== at 0x38066A08: ??? (in
> /home/elem/local/lib/valgrind/none-x86-linux)
> ==31001== by 0x38066B2B: report_and_quit (m_libcassert.c:225)
> ==31001== by 0x38066CB5: panic (m_libcassert.c:277)
<<snip deep stack trace>>
You've probably run out of stack space while inside valgrind.
The question is whether you ran out of stack space in your program, too
("before" the most recent transition from your program "into valgrind".)
> OS. Redhat 7.1 with gcc-3.0, binutils-2.18.
Which version of valgrind?
[Red Hat 7.1 is about ten years old!]
--
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users