Message: Re: Strange Segmentation fault Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Strange Segmentation fault  

Forum: Multithreading
Re: Question Strange Segmentation fault (Volodymyr Rodin)
Re: None Re: Strange Segmentation fault (Makoto Asai)
Re: None Re: Strange Segmentation fault (Volodymyr Rodin)
Re: None Re: Strange Segmentation fault (Makoto Asai)
Re: None Re: Strange Segmentation fault (Volodymyr Rodin)
Re: None Re: Strange Segmentation fault (Volodymyr Rodin)
Date: Nov 19, 05:56
From: John Allison <John Allison>

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.

Cheers, John

 Add Message Add Message
to: "Re: Strange Segmentation fault "

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews