Problem 413 - Crash due to problem in G4Polycone
Summary: Crash due to problem in G4Polycone
Status: RESOLVED WORKSFORME
Alias: None
Product: Geant4
Classification: Unclassified
Component: geometry (show other problems)
Version: 4.1
Hardware: PC Linux
: P2 normal
Assignee: Gabriele Cosmo
URL:
Depends on:
Blocks:
 
Reported: 2002-09-23 10:09 CEST by Pedro.Arce
Modified: 2003-03-10 02:55 CET (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description Pedro.Arce 2002-09-23 10:09:20 CEST 
The DistanceToOut method of a G4Polycone returns a too big distance and then it
crashes in G4VoxelNavigation::ComputeStep.
You can find the description of the volume giving the problem at
http://cmsdoc.cern.ch/~arce/oscar/g4-bad_polycone/geometry.lis

I have added a printout in each DistanceXXX method of G4VCSGFaceted. You can see
the output at
http://cmsdoc.cern.ch/~arce/oscar/g4-bad_polycone/g4.out
Comment 1 davidw 2002-10-08 21:34:59 CEST 
The very helpful diagnostic output included in this problem report
indicates that G4Polycone::DistanceToOut was invoked illegally with
a position that is outside its boundaries. It is not clear why this
happened, but it does not appear that a previous call to G4Polycone
was the reason.
Comment 2 Gabriele Cosmo 2003-03-10 02:55:59 CET 
We could not reproduce the problem with the tests we have currently available
and further investigations we could do. It would be extremely useful if you
could provide us with a test case with a geometrical shape similar to the one
used in your setup, so we can reproduce it. Thanks.