Problem 1377 - Crash at run time with QT ON, geant4-09-05-ref-10
Summary: Crash at run time with QT ON, geant4-09-05-ref-10
Status: RESOLVED FIXED
Alias: None
Product: Examples/Extended
Classification: Unclassified
Component: medical/DICOM (show other problems)
Version: 9.5
Hardware: All Mac OS X
: P5 major
Assignee: garnier
URL:
Depends on:
Blocks:
 
Reported: 2012-11-08 17:02 CET by garnier
Modified: 2012-11-19 16:29 CET (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description garnier 2012-11-08 17:02:35 CET 
On Mac OS X 10.8 :

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminate called throwing an exception
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8fb5e212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff91127af4 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff9116bdce abort + 143
3 libc++abi.dylib 0x00007fff9218da17 abort_message + 257
4 libc++abi.dylib 0x00007fff9218b3c6 default_terminate() + 28
5 libobjc.A.dylib 0x00007fff8bdda887 _objc_terminate() + 111
6 libc++abi.dylib 0x00007fff9218b3f5 safe_handler_caller(void (*)()) + 8
7 libc++abi.dylib 0x00007fff9218b450 std::terminate() + 16
8 libc++abi.dylib 0x00007fff9218c5b7 __cxa_throw + 111
9 libG4processes.dylib 0x000000010ab97388
G4ComponentSAIDTotalXS::Initialise(G4SAIDCrossSectionType) + 168
10 libG4processes.dylib 0x000000010ab9716e
G4ComponentSAIDTotalXS::GetInelasticIsotopeCrossSection(G4ParticleDefinition
const*, double, int, int) + 142
11 libG4processes.dylib 0x000000010ab464f8
G4BGGNucleonInelasticXS::BuildPhysicsTable(G4ParticleDefinition const&)
+ 1512
12 libG4processes.dylib 0x000000010ab9aa61
G4CrossSectionDataStore::BuildPhysicsTable(G4ParticleDefinition const&) + 65
13 libG4processes.dylib 0x000000010abbe6c5
G4HadronicProcess::BuildPhysicsTable(G4ParticleDefinition const&) + 21
14 libG4run.dylib 0x000000010a863ded
G4VUserPhysicsList::BuildPhysicsTable(G4ParticleDefinition*) + 733
15 libG4run.dylib 0x000000010a865079
G4VUserPhysicsList::BuildPhysicsTable() + 873
16 libG4run.dylib 0x000000010a85be4b
G4RunManagerKernel::BuildPhysicsTables() + 107
17 libG4run.dylib 0x000000010a85bcc5
G4RunManagerKernel::RunInitialization() + 149
18 libG4run.dylib 0x000000010a857a3c G4RunManager::RunInitialization() + 28
19 libG4run.dylib 0x000000010a857369 G4RunManager::BeamOn(int, char
const*, int) + 57
Comment 1 Ivana Hrivnacova 2012-11-14 16:51:35 CET 
The example breaks when G4SAIDXSDATA variable is not defined;
when running on FC14 we get:
./DICOM run.in
In /work/packages/geant4/geant4_ref_source/source/processes/hadronic/cross_sections/src/G4ComponentSAIDTotalXS.cc, line 245: 
===> NO data sets opened
terminate called after throwing an instance of 'G4HadronicException'
  what():  std::exception
Aborted (core dumped)

The G4HadronicException class throws a "real" exception which seems not be caught anywhere.
Comment 2 Ivana Hrivnacova 2012-11-14 17:00:41 CET 
When running the same example with Qt GUI, we get:
terminate called after throwing an instance of 'G4HadronicException'
  what():  std::exception
Aborted (core dumped)

The message 
===> NO data sets opened
does not appear anywhere in this case.
Comment 3 garnier 2012-11-19 16:29:24 CET 
Fixed by hadr-cross-V09-05-42

Laurent