Problem 1593 - Using G4WrapperClass.cc to implement bremsstrahlung splitting causes crash in version 10.0
Summary: Using G4WrapperClass.cc to implement bremsstrahlung splitting causes crash in...
Status: RESOLVED DUPLICATE of problem 1594
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/biasing (show other problems)
Version: 10.0
Hardware: All All
: P5 normal
Assignee: alexander.howard
URL:
Depends on:
Blocks:
 
Reported: 2014-03-19 19:15 CET by MJM
Modified: 2014-03-19 19:19 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description MJM 2014-03-19 19:15:48 CET
Overview: Registering G4eBremsstrahlung to a G4WrapperClass and then adding this WrapperClass to the PhysicsList in order to bias the process (e.g. bremsstrahlung splitting) causes the program to crash while executing. The crash occurs in Geant4 version 10.0-patch1, but not in Geant4 version 9.6. The crash report is added below in the additional information section.

Steps to Reproduce: Attached one will find a very basic program with bremsstrahlung splitting implemented with the G4WrapperClass. After building the program, one can turn bremsstrahlung splitting on and off either with the UI-commands or by simply editing the run.mac file and running the program with it. 

Actual Results: The programs crashes in version 10.0 with activated bremsstrahlung splitting (BremsstrahlungSplittingFlag set to true). If bremsstrahlung splitting is deactivated the programs executes correctly. Using Geant4 version 9.6. the program executes correctly either way and activated bremsstrahlung splitting achieves the wanted biasing of the physics.

Expected Results: The programs should not crash.

Build Date & Platform: Build Date 12-03-14 on Mac OSX 10.9.2

Additional Builds and Platforms: Does occur as well on Windows 7.

Additional Information: - The crash occurs even if one greatly simplifies the BremsstrahlungSplitting class, so that the process is not biased at all.


- A forum discussion regarding this problem can be found here: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/biasing_scoring/112.html


Crash report:

=========================================================== There was a crash. This is the entire stack trace of all threads: ===========================================================

Thread 1 (process 6353):

#0  0x00007fff842166ac in wait4 ()
#1  0x00007fff83db4002 in system ()
#2  0x000000010dd3af49 in TUnixSystem::StackTrace ()
#3  0x000000010dd38aa4 in TUnixSystem::DispatchSignals ()
#4  <signal handler called>
#5  0x000000010c5af903 in G4LossTableBuilder::BuildDEDXTable ()
#6  0x000000010c5b3fe7 in G4LossTableManager::BuildTables ()
#7  0x000000010c5b390b in G4LossTableManager::BuildPhysicsTable ()
#8  0x000000010c5c0b2f in G4VEnergyLossProcess::BuildPhysicsTable ()
#9  0x000000010c267f02 in G4VUserPhysicsList::BuildPhysicsTable ()
#10 0x000000010c2672a4 in G4VUserPhysicsList::BuildPhysicsTable ()
#11 0x000000010c254141 in G4RunManagerKernel::BuildPhysicsTables ()
#12 0x000000010c253f79 in G4RunManagerKernel::RunInitialization ()
#13 0x000000010c247f94 in G4RunManager::RunInitialization ()
#14 0x000000010c247d37 in G4RunManager::BeamOn ()
#15 0x000000010c25cb2b in G4RunMessenger::SetNewValue ()
#16 0x000000010db060a7 in G4UIcommand::DoIt ()
#17 0x000000010db1cfdd in G4UImanager::ApplyCommand ()
#18 0x000000010dafecad in G4UIbatch::ExecCommand ()
#19 0x000000010dafeeb8 in G4UIbatch::SessionStart ()
#20 0x000000010db1a5d9 in G4UImanager::ExecuteMacroFile ()
#21 0x000000010db165fe in G4UIcontrolMessenger::SetNewValue ()
#22 0x000000010db060a7 in G4UIcommand::DoIt ()
#23 0x000000010db1cfdd in G4UImanager::ApplyCommand ()
#24 0x000000010bacbe6c in main ()

===========================================================

The lines below might hint at the cause of the crash. If they do not help you then please submit a bug report at http://root.cern.ch/bugs. Please post the ENTIRE stack trace from above as an attachment in addition to anything else that might help us fixing this issue. ===========================================================

#5  0x000000010c5af903 in G4LossTableBuilder::BuildDEDXTable ()
#6  0x000000010c5b3fe7 in G4LossTableManager::BuildTables ()
#7  0x000000010c5b390b in G4LossTableManager::BuildPhysicsTable ()
#8  0x000000010c5c0b2f in G4VEnergyLossProcess::BuildPhysicsTable ()
#9  0x000000010c267f02 in G4VUserPhysicsList::BuildPhysicsTable ()
#10 0x000000010c2672a4 in G4VUserPhysicsList::BuildPhysicsTable ()
#11 0x000000010c254141 in G4RunManagerKernel::BuildPhysicsTables ()
#12 0x000000010c253f79 in G4RunManagerKernel::RunInitialization ()
#13 0x000000010c247f94 in G4RunManager::RunInitialization ()
#14 0x000000010c247d37 in G4RunManager::BeamOn ()
#15 0x000000010c25cb2b in G4RunMessenger::SetNewValue ()
#16 0x000000010db060a7 in G4UIcommand::DoIt ()
#17 0x000000010db1cfdd in G4UImanager::ApplyCommand ()
#18 0x000000010dafecad in G4UIbatch::ExecCommand ()
#19 0x000000010dafeeb8 in G4UIbatch::SessionStart ()
#20 0x000000010db1a5d9 in G4UImanager::ExecuteMacroFile ()
#21 0x000000010db165fe in G4UIcontrolMessenger::SetNewValue ()
#22 0x000000010db060a7 in G4UIcommand::DoIt ()
#23 0x000000010db1cfdd in G4UImanager::ApplyCommand ()
#24 0x000000010bacbe6c in main ()

===========================================================
Comment 1 MJM 2014-03-19 19:19:19 CET
Accidently submitted the same problem twice. Sorry!

*** This problem has been marked as a duplicate of problem 1594 ***