|Message: RE: Segmentation Fault in G4RToEConvForGamma::BuildAbsorptionLengthVector ()||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hi, Thank You for your quick reply, sorry I should of made it clearer my physics list should be exactly the same as in N03 (copied and pasted with a few variable modifications). I have however noticed since that when I try to use G4cout to read out the materials used in the detector construction method in G4UserDetectorConstruction::Construct() that it causes a segmentation fault. The materials are defined in a subroutine of detectorconstruction::detectorconstruction() as per example N04. As this is the second argument to the troublesome function G4RToEnergy... could this be the source of the original error? I think the problem with the G4cout is the scope of the material variables defined in the header but I have tried to change this ensuring every variable is public but u still get the same problem. Does Geant change the scope of these variables at any point? The G4cout does work when placed in the define materials subroutine however. I'm still open to the suggestion that my physics list could be wrong and will check through that now. Any suggestions would be gratefully received. Alan
|Inline Depth:||Outline Depth:||Add message:|