I am running a simple air shower simulation and it seems to entering an infinit loop in part of the G4BinaryCascade. More precisely in G4Scatterer::GetTimeToInteraction(). Below is gdb printout: Program received signal SIGINT, Interrupt. 0x082c1a92 in G4Scatterer::GetTimeToInteraction () (gdb) where #0 0x082c1a92 in G4Scatterer::GetTimeToInteraction () #1 0x082c2549 in G4Scatterer::GetCollisions () #2 0x0814b16b in G4BinaryCascade::FindCollisions () #3 0x08146dfe in G4BinaryCascade::ApplyYourself () #4 0x085598d5 in G4HadronicProcess::GeneralPostStepDoIt () #5 0x0855e174 in G4HadronInelasticProcess::PostStepDoIt () #6 0x08959c2d in G4SteppingManager::InvokePSDIP () #7 0x08959b93 in G4SteppingManager::InvokePostStepDoItProcs () #8 0x0895b64b in G4SteppingManager::Stepping () #9 0x089460c4 in G4TrackingManager::ProcessOneTrack () #10 0x08914709 in G4EventManager::DoProcessing () #11 0x08914ca9 in G4EventManager::ProcessOneEvent () #12 0x088d818d in G4RunManager::DoEventLoop () #13 0x088d78f1 in G4RunManager::BeamOn () #14 0x088e5b5b in G4RunMessenger::SetNewValue () #15 0x08aac8c8 in G4UIcommand::DoIt () #16 0x08ac4ed0 in G4UImanager::ApplyCommand () #17 0x08ad6909 in G4UIbatch::SessionStart () #18 0x08abf810 in G4UImanager::ExecuteMacroFile () #19 0x08adcf61 in G4UIcontrolMessenger::SetNewValue () #20 0x08aac8c8 in G4UIcommand::DoIt () #21 0x08ac4ed0 in G4UImanager::ApplyCommand () #22 0x08ac38aa in G4UImanager::ApplyCommand () #23 0x0804f89e in main () #24 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6
thank you for reporting this. I'll have a look, but would need more information. Can you get a hand on the reaction conditions, so I can reproduce this in a unit test (particle type, kinetic energy, material)? Many greetings, Hans-Peter.
It was a air shower simulation so the likely target were O, N and Ar. It happened to both proton and alpha incidences and in the case of proton the incident energy was ~ 5 GeV. Regards Fan
Dear Fan, this one is harder to reproduce than expected. Is it possible for you to put the application someplace I can get it, so I can try and reproduce the problem 'in situ'? Many greetings, Hans-Peter.
Dear Hans-Pete, I cannot reproduce this bug with the lattest version of G4 (6.2 patch-1), so I assume it has been "fixed" due to other changes introduced since I first reported this problem. I guess you can change status of this bug to "fixed" for now and I will keep monitoring the situation and hopefully it will not re-appear. Regards. Fan I will
