When changing from 4.1.1_ref01 to 4.2.0_ref01 the follwoing exceptions shows up. Hans-Peter suggests it is related to update of a solids in 'MagneticField' Stephan G4EventManager::ProcessOneEvent(this = 0x1fa5718, anEvent = 0x1f77738) G4TrackingManager::ProcessOneTrack(this = 0x1f7ca78, apValueG4Track = 0x2cb0a80) G4SteppingManager::Stepping(this = 0x1fa5758) G4SteppingManager::DefinePhysicalStepLength(this = 0x1fa5758) G4Transportation::AlongStepGetPhysicalInteractionLength(this = 0x250d208, track = CLASS, previousStepSize = 3.186024785405, currentMinimumStep = 2.5328778320636, currentSafety = 0.0, selection = 0x1fa588c) G4PropagatorInField::ComputeStep(this = 0x1fa7258, pFieldTrack = CLASS, CurrentProposedStepLength = 2.5328778320636, currentSafety = 0.0, pPhysVol = 0x21671b0) G4Navigator::ComputeStep(this = 0x1fa60c0, pGlobalpoint = CLASS, pDirection = CLASS, pCurrentProposedStepLength = 2.420533299437, pNewSafety = 233.41857147186) G4NormalNavigation::ComputeStep(this = 0x1fa6168, localPoint = CLASS, localDirection = CLASS, currentProposedStepLength = 2.420533299437, newSafety = 233.41857147186,history = CLASS, validExitNormal = 0, exitNormal = CLASS, exiting = 0, entering = 0, pBlockedPhysical = 0x1fa60e4, blockedReplicaNo = -1) G4Box::DistanceToOut(this = 0x2166fb8, p = CLASS) G4Exception(s = 0x14a267c "Invalid call in G4Box::DistanceToOut(p), point p is outside") abort(0xeec2227c, 0x6, 0x9744d246, 0xeed671e0, 0xef129c20, 0xc18524f3)
The problem is currently under investigation and a temporary solution has been committed to testing (tag "geom-solids-csg-V02-00-02" for the module geometry/solids/CSG), you can try it out if you wish.
*** Bug 98 has been marked as a duplicate of this bug. *** *** 'Vladimir.Grichine@cern.ch' will be responsible for bug 98. ***
*** Bug 101 has been marked as a duplicate of this bug. *** *** 'Vladimir.Grichine@cern.ch' will be responsible for bug 101. ***
*** Bug 219 has been marked as a duplicate of this bug. *** *** 'Vladimir.Grichine@cern.ch' will be responsible for bug 219. ***
*** Bug 297 has been marked as a duplicate of this bug. *** *** 'Vladimir.Grichine@cern.ch' will be responsible for bug 297. ***
This problem report is closed. Fixes are included in Release 4.0, patch-01 (or patch-02).