Hi, The c++-filt error is annoying but not fatal and means that the demangling for the printout is not going to be properly done. This is due to the call to c++filt not being (yet) properly done for every single possible compiler version and configuration. Currently the only way to 'fix' the problem is to go hack unix/src/TUnixSystem.cxx and recompile ROOT. Anyway, the call to c++filt is made because your code (or possible ROOT code) executed an illegal operation. I.e. your program just naturally core dumped and ROOT is trying to give you some information on where. Cheers, Philippe. -----Original Message----- From: owner-roottalk@pcroot.cern.ch [mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of Damien PRIEUR Sent: Friday, August 01, 2003 9:59 AM To: roottalk@pcroot.cern.ch Subject: [ROOT] /usr/bin/c++filt: unknown demangling style `gnu-v3' Hi, I am currently using Root 3.05.05 on linux redhat 7.3, located at Cern under /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/ I launch root and execute a simple macros(see attachment) which basicaly open few files, get some tree and draw few histograms: >.x ana_NRJ_sw.C and then I get: > *** Break *** segmentation violation > Generating stack trace... >/usr/bin/c++filt: unknown demangling style `gnu-v3' when I launch root with gdb and then backtrace it, I get: Program received signal SIGSEGV, Segmentation fault. 0x40608314 in G__ST_p0_pointer () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so (gdb) bt #0 0x40608314 in G__ST_p0_pointer () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #1 0x40603396 in G__exec_asm () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #2 0x405f65bb in G__exec_loop () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #3 0x405f6a29 in G__exec_for () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #4 0x405f8f34 in G__exec_statement () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #5 0x40587dca in G__exec_tempfile_core () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #6 0x4058803f in G__exec_tempfile () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #7 0x40601629 in G__process_cmd () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCint.so #8 0x4015832e in TCint::ProcessLine(char const*, TInterpreter::EErrorCode*) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #9 0x40158431 in TCint::ProcessLineSynch(char const*, TInterpreter::EErrorCode*) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #10 0x400da044 in TApplication::ProcessFile(char const*, int*) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #11 0x400d97de in TApplication::ProcessLine(char const*, bool, int*) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #12 0x40d8af4e in TRint::HandleTermInput() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libRint.so #13 0x40d89d35 in TTermInputHandler::Notify() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libRint.so #14 0x40d8b772 in TTermInputHandler::ReadNotify() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libRint.so #15 0x401adc2d in TUnixSystem::CheckDescriptors() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #16 0x401ad30a in TUnixSystem::DispatchOneEvent(bool) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #17 0x40128a2f in TSystem::InnerLoop() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #18 0x401289bd in TSystem::Run() () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #19 0x400da24e in TApplication::Run(bool) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libCore.so #20 0x40d8aadb in TRint::Run(bool) () from /afs/cern.ch/sw/root/v3.05.05/rh73_gcc32/root/lib/libRint.so #21 0x08048890 in main () #22 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 Does anybody know the meaning of this error message: '/usr/bin/c++filt: unknown demangling style `gnu-v3'' and how to get rid of it ? Or is it my macro which is not correct and lead to this crash ? Thanks in advance, Damien Prieur.
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:14 MET