|Message: RE: AIDAJNI and "gdb"||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
> 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 Tony
|Inline Depth:||Outline Depth:||Add message:|