RE: [ROOT] How to debug SegVs received at the root prompt?

From: Philippe Canal (pcanal@fnal.gov)
Date: Mon Jul 30 2001 - 19:22:34 MEST 

> When I run under GDB,
> root "eats" the SegV signal and keeps running so I can't even get a
> stack trace.  Any suggestions?

Hi Brett,

This is not my experience.  To debug this type of problem I usually just
have to do (note the .exe even on linux).
	gdb root.exe
	> run
root [0] gSystem->Load("....");
root [1] gSystem->Load("....");
root [2] m = new MyObject()
	> shared 

The shared command loads the shared libraries symbol.

Philippe.
	
-----Original Message-----
From: owner-roottalk@pcroot.cern.ch
[mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of Brett Viren
Sent: Monday, July 30, 2001 11:17 AM
To: roottalk@pcroot.cern.ch
Subject: [ROOT] How to debug SegVs received at the root prompt?


Hi.

I have a custom library which I dynamically link into the root app,
along with the others on which it depends.  Then, durring the creation
ofan object from this library I get a segmentation violation.

The session goes a little like this:

root [0] gSystem->Load("....");
root [1] gSystem->Load("....");
root [2] m = new MyObject()
 ...
 *** Break *** segmentation violation
Root > 


2 questions:

 - What, if anything is the meaning of the change of root prompt
 style?

 - More importantly, is there some way to debug this SegV without
 peppering the code with a lot of "cerr<<"s?  When I run under GDB,
 root "eats" the SegV signal and keeps running so I can't even get a
 stack trace.  Any suggestions?

Thanks,
-Brett.

This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:53 MET