Hi Thomas, When you get this kind of crash in your application, there are 2 things that you can do: - run your application under gdb and look at the traceback, eg gdb root.exe root > dosomething that generates the crash gdb > bt By looking at the output of bt, you will get more information on the place of the crash. If the crash happens in one of your classes, compile the class in debug mode. bt will tell you the line number and you can inspect the class variables. - Very often a segm violation is due to the use of a null pointer or a non-initialized pointer. Check your constructors in particular. But the best way is to use the valgrind tool that is extremely simple to use.eg, valgrind root.exe root > dosomething valgrind will report the use of uninitialized variables and also potential memory leaks. You can also use valgring together with gdb. Really a powerful tool. Rene Brun On Fri, 23 May 2003, Thomas Eberl wrote: > Dear ROOTers, > > > - i am using RH 8.0 on a AMD Athlon 2200+. > (with glibc-2.2.93-5) > - i have compiled ROOT 305-05 with gcc version 3.2 20020903 (Red Hat > Linux 8.0 3.2-7) > without problems > > my code also compiles without any problems, but crashes, when I try to > run a CINT macro: > > error<TUnixSystem::DispatchSignals>:segmentation violation > Generating stack trace... > 0x401a06fe in TUnixSystem::StackTrace() + 0x36c from > /home/teberl/root/lib/libCore.so > 0x4019f2c2 in TUnixSystem::DispatchSignals(ESignals) + 0x7a from > /home/teberl/root/lib/libCore.so > 0x4019e4d3 in <unknown> from /home/teberl/root/lib/libCore.so > 0x401a1ee1 in <unknown> from /home/teberl/root/lib/libCore.so > 0x40cbf47e in <unknown> from /lib/i686/libpthread.so.0 > 0x42028c48 in <unknown> from /home/teberl/root/bin/root.exe > > > The same code and macro works on a > - Pentium 4 > - RH7.3 > - gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) > - ROOT 303-09 (binaries) > - glibc-2.2.5-43 > > system without any problem. > > > > Do you have a hint for me ? > > Thanks > > Thomas Eberl >
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:11 MET