|
From: Dave S. <dgs...@nu...> - 2006-11-01 20:22:03
|
First of all, thanks for your replies. Julian Seward writes: > > > ==26931== Process terminating with default action of signal 6 (SIGABRT): > > dumping core > > ==26931== at 0x4159805: raise (in /lib/tls/libc-2.3.3.so) > > ==26931== by 0x415B1E8: abort (in /lib/tls/libc-2.3.3.so) > > ==26931== by 0x40CD7C4: __cxxabiv1::__terminate(void (*)()) > > (in /usr/lib/libstdc++.so.5.0.6) > > ==26931== by 0x40CD801: std::terminate() > > (in /usr/lib/libstdc++.so.5.0.6) > > ==26931== by 0x40CD981: __cxa_throw (in > > /usr/lib/libstdc++.so.5.0.6) > > ==26931== by 0x40CDBC2: operator new(unsigned) > > (in /usr/lib/libstdc++.so.5.0.6) > > ==26931== by 0x817BA03: boost::any::any<float>(float const&) (any.hpp:33) > > ==26931== by 0x817B9D9: Numerica::PropertyWrapper ... > > ==26931== by 0x817B968: void Numerica::Properties::setProperty ... > > ==26931== by 0x81797A4: void Numerica::ExternalProperties ... > > ==26931== by 0x81782D6: Numerica::ONIRMessageTranslator: > > ==26931== by 0x8176FA9: Numerica::ONIRMessageTranslator ... > > My first reaction to this is that operator new(unsigned) decided to throw > an exception and terminate the program with SIGABRT. Why? I don't know, > but one obvious guess is that it thought it was out of memory for whatever > reason. > > We had an obscure runs-on-memcheck fails-on-other-tools bug in 3.2.0 but > that was fixed in 3.2.1. Maybe this is a new variant. > > What happens if you run it with --tool=none (instead of --tool=callgrind) ? > Does it work? Nope. Results appended below. > If no, try these combinations: > > --tool=none --vex-iropt-level=1 > --tool=none --vex-iropt-level=0 > --tool=none --sanity-level=3 > --tool=none --sanity-level=4 Will do. Secondly, Olivier Ballereau wrote > Dave Steffen wrote: > > Compiler: GCC 3.4.6 > > Reading specs from /scratch/dgsteffen/local/lib/gcc/i686-pc-linux-gnu/3.4.6/specs > > Configured with: ../gcc-3.4.6/configure --prefix=/scratch/dgsteffen/local > > Thread model: posix > > gcc version 3.4.6 > ... > > --7122-- Reading syms from /usr/lib/libstdc++.so.5.0.6 (0x403D000) > > I think it can be a libstdc++ version problem. According to > <http://gcc.gnu.org/onlinedocs/libstdc++/abi.html>, G++ 3.4.6 ships with > libstdc++.so.6.0.3. Moreover, your GCC is configured with > --prefix=/scratch/dgsteffen/local (and seems to be installed there, > according to the specs file) and libstdc++ is loaded from /usr/lib. > > This would explain why memcheck has no problem (the call to operator > new() is redirected to memcheck's own version), but causes problem to > callgrind. This is also very possible. I'll try recompiling with GCC 3.3, which doesn't do this, and is also not installed in my "special bunch o' tools" directory, and try again. Thanks! ---------------------------------------------------------------------- Dave Steffen, Ph.D. Software Engineer IV Disobey this command! Numerica Corporation ph (970) 419-8343 x27 fax (970) 223-6797 - Douglas Hofstadter dgs...@nu... ___________________ Numerica Disclaimer: This message and any attachments are intended only for the individual or entity to which the message is addressed. It is proprietary and may contain privileged information. If you are neither the intended recipient nor the agent responsible for delivering the message to the intended recipient, you are hereby notified that any review, retransmission, dissemination, or taking of any action in reliance upon, the information in this communication is strictly prohibited, and may be unlawful. If you feel you have received this communication in error, please notify us immediately by returning this Email to the sender and deleting it from your computer. |