In my XXXPhysicsList.cc class I noticed the following problem in the SetCuts method. Calling in that order SetCutValue(cutForElectron,"e+"); SetCutValue(cutForElectron,"e-"); produces a crash at execution, while the opposite: SetCutValue(cutForElectron,"e-"); SetCutValue(cutForElectron,"e+"); is ok.
Warning + G4Exception have been put into G4eIonisation.cc and G4eIonisationPlus.cc to avoid calling SetCut for e+ before e-. ( We need the energy cuts for ELECTRON to compute the energy loss or mean free path for positron!)