|Message: Re: Strange Segmentation fault||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)|
Thankyou for this. It does indeed look like a threading issue. I do not get your symptoms myself but I will give the code a threading health check. Your investigation at least pins it down to a particular place. That message os one of the few messages that is printed by the vis manager while in the event loop thread. Adding /vis/modeling/trajectories/create/drawByCharge suppresses this message. So I suspect it is to do with writing to G4cout from the vis event loop thread. But as I said, I do not get this symptom even when I my app prints
G4VIS > G4VisManager: Using G4TrajectoryDrawByCharge as fallback trajectory model.
so it going to be difficult to debug.
I am pleased you have found a workaround.