|Message: Re: Problems with G4TouchableHistory||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)|
Thank you Andrea! Indeed it seemed to be a static problem of a variable decleration. After solving it runs now until the end.
On Thu, 13 Aug 2015 19:21:20 GMT, Andrea Dotti wrote:
> Hello, from your report it seems that the problem is somewhere in the > method SensDetPMT::ProcessHits, without seeing the details of the code > it is difficult to know where the problem is, in MT even if the code > crashes when the lines you have provided are present, the real problem > may be somewhere else. > > Please consider to: - double check that the SensitiveDetector is created > and associated to the LogicalVolume in the ConstructSDandField() method > of the detector construction class. - There are no shared variables in > the SD code which access is not protected (e.g. no static) - Recompile > your code in Debug mode (e.g. cmake flag -DCMAKE_BUILD_TYPE=Debug) that > could give you more information on the exact location the crash happens > - In gdb use "info threads" and check the status of all threads (you > have provided the stacktrace of only one of them that may well be the > one that did not cause the crash) > > I hope this can be of help, Andrea Dotti >