> ***G4EleNucCrS::GetEquPhotE:S=3.5801>8.73125e-246,l=97<335 > **G4EleNucCS::GetEfPhE:L=97,S=3.5801,Y=8.73125e-246 > ***G4ElectroNuclearCrossSection::GetEquPhotE:1.26411e+07>3.62992,S=3.5801,ris=1.15197,B=125,E=97,Y=8.73125e-246 > G4ElectroNuclearReaction::ApplyYourself: photonEnergy is very high > If this condition appears frequently, please contact > Hans-Peter.Wellisch@cern.ch > > Program received signal SIGSEGV, Segmentation fault. > 0x2e879744 in G4ParticleChange::Initialize () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4track.so > (gdb) where > #0 0x2e879744 in G4ParticleChange::Initialize () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4track.so > #1 0x2d9c448f in G4TheoFSGenerator::ApplyYourself () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_HE_gen.so > #2 0x2f54099a in G4ElectroNuclearReaction::ApplyYourself () from > /afs/cern.ch/cms/Releases/OSCAR/OSCAR_2_0_0_pre0/lib/Linux__2.2/libCMSProductionPhysics.so > #3 0x2e4ea880 in G4HadronicProcess::GeneralPostStepDoIt () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_mgt.so > #4 0x2e4e8cc4 in G4HadronInelasticProcess::PostStepDoIt () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_mgt.so > #5 0x2e6270a6 in G4SteppingManager::InvokePostStepDoItProcs () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4tracking.so > #6 0x2e624901 in G4SteppingManager::Stepping () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4tracking.so > #7 0x2e62d195 in G4TrackingManager::ProcessOneTrack () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4tracking.so > #8 0x2e5bc5e7 in G4EventManager::ProcessOneEvent () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4event.so > > > Actually, there is a bit of history... > In the first attempt I got > > G4PropagateInField: Warning: Particle is looping - tracking in field will > be stopped. > It has performed 10000 steps in Field while a maximum of 10000 are > allowed. > G4PropagateInField: Warning: Looping particle. > G4Transportation is killing track that is looping or stuck > This track has 0.194042 MeV energy. > **G4EleNucCS::GetEfPhE:L=107,S=4.32449,Y=nan > zsh: 6965 segmentation fault oscar > > at the second event, > > and in the second attempt I got: > > Program received signal SIGSEGV, Segmentation fault. > 0x2e879744 in G4ParticleChange::Initialize () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4track.so > (gdb) where > #0 0x2e879744 in G4ParticleChange::Initialize () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4track.so > #1 0x2d9c448f in G4TheoFSGenerator::ApplyYourself () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_HE_gen.so > #2 0x2f54099a in G4ElectroNuclearReaction::ApplyYourself () from > /afs/cern.ch/cms/Releases/OSCAR/OSCAR_2_0_0_pre0/lib/Linux__2.2/libCMSProductionPhysics.so > #3 0x2e4ea880 in G4HadronicProcess::GeneralPostStepDoIt () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_mgt.so > #4 0x2e4e8cc4 in G4HadronInelasticProcess::PostStepDoIt () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4hadronic_mgt.so > #5 0x2e6270a6 in G4SteppingManager::InvokePostStepDoItProcs () from > /afs/cern.ch/sw/geant4/releases/specific/i386_redhat61/gcc-2.95.2/geant4.4.1.p01/lib/libG4tracking.so > > at the first event. >
Turns out to be not so trivial. What happens is that the correction of y gows wrong, if the electron falls below reaction threshold during the step. Still working... Hans-Peter.
workaround in place for the release, fix needs still to be worked on.
fixed in 5.0.
released in 5.0