> I have verified that this works on with the ROOT 4.00.08a version > download and compiled this morning. I assume that by 'this works', you meant that you can still reproduce the crash. Anyway, this sounds like a potential double deletion or other memory corruption. You should run your application in the debugger to see a real stack trace. You also should make sure that all the library that you are using are in sync (i.e. recompiled) with the version of ROOT you are using. Cheers, Philippe. -----Original Message----- From: owner-roottalk@pcroot.cern.ch [mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of John Pretz Sent: Monday, August 16, 2004 11:51 AM To: roottalk@pcroot.cern.ch Subject: [ROOT] Crash on exit Hi Roottalk, I've got a pretty nasty problem. Well, nasty for me, but not necessarily for y'all. I've got an application that I swear ran before. Now it is crashing. There is a central object that makes up the application, and I call methods of that application via CINT. When all is done, I do an exit(0) to return to the shell from the root script. The program proceeds just as it should... until the exit(0). When I get to exit(0) I get the following output: Generating stack trace... 0xb63e75b3 in exit + 0x63 from /lib/tls/libc.so.6 0xb71af88f in TUnixSystem::Exit(int, bool) + 0x25 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb728e94f in <unknown> from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb6e54aae in G__call_cppfunc + 0x263 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e443d7 in G__interpret_func + 0x6e4 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e2c026 in G__getfunction + 0x134a from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6eaff28 in G__getstructmem + 0x82a from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6eaa041 in G__getvariable + 0x4db from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e23622 in G__getitem + 0x5c1 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e2223a in G__getexpr + 0x783e from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e699c0 in G__exec_function + 0x1d5 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e7060d in G__exec_statement + 0x23eb from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e0b44f in G__exec_tempfile_core + 0x2ce from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e0b659 in G__exec_tempfile + 0x22 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb6e783a7 in G__process_cmd + 0x4174 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCint.so 0xb7144d69 in TCint::ProcessLine(char const*, TInterpreter::EErrorCode*) + 0xa9 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb7144e76 in TCint::ProcessLineSynch(char const*, TInterpreter::EErrorCode*) + 0x46 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb70b757a in TApplication::ProcessFile(char const*, int*) + 0x846 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb70b6cb9 in TApplication::ProcessLine(char const*, bool, int*) + 0x523 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libCore.so 0xb660583d in TRint::Run(bool) + 0x1a3 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/lib/libRint.so 0x080488dd in main + 0x71 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/bin/root.exe 0xb63d2768 in __libc_start_main + 0xf8 from /lib/tls/libc.so.6 0x080487e1 in _Unwind_Resume + 0x31 from /extra/pretz/home/work-data/tools/Linux-i386/lib/root/bin/root.exe I also get the same error when I .q from the root session should I omit the exit(0) from the script. I have verified that this works on with the ROOT 4.00.08a version download and compiled this morning. I'm on a Red Hat Enterprise Linux WS box. I can't find anything in roottalk about this. Has anyone else had their programs fail this way? Thanks for the help. John
This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:09 MET