Message: RE: AIDAJNI and "gdb" Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None RE: AIDAJNI and "gdb" 

Forum: Analysis
Re: None AIDAJNI and "gdb" (Fan Lei)
Date: 16 Sep, 2004
From: <>

> I have a program which work fine normally but crash when run 
> under "gdb". The backtrace data seems to suggest a problem 
> with AIDAJNI.
> My question is can program linked to AIDAJNI be run under 
> "gdb", if not what is the right tool to use for debugging.

Hi Fan, I don't use gdb (I debug on windows) but I did find a couple of hints which might help you. First SIGSEGV's are normal for Java programs -- they use SIGSEGV's to trap null pointer exceptions, but they are caught and handled by the Java virtual machine and do not indicate that anything is wrong.

Of course gdb doesn't know this, so it stops when it sees the SIGSEGV. You can stop this from happening by issuing the command:

gdb> handle SIGSEGV pass nostop

This causes gdb to pring a message but continue. Of course this will also prevent gdb stopping if some problem in your geant4 program causes a SIGSEGV that you do care about, so you will probably have to experiment a little.

One other problem which doesn't appear to have affected you, but did affect me when I tried to use gdb to reproduce your problem is something to do with linux kernels, NPTL threads and Java use of threads. Anyway if gdb simply hangs after starting Java try first setting the following environment variable 

  setenv LD_ASSUME_KERNEL 2.2.5


Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: RE: AIDAJNI and "gdb"   (Fan Lei - 17 Sep, 2004)
 Add Message Add Message
to: "RE: AIDAJNI and "gdb""

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]