Message: Segmentation Violation issue Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Segmentation Violation issue 

Forum: Geometry
Date: 04 Jun, 2018
From: Jack Gallant <Jack Gallant>

Hello all,

I came across an issue when adding volumes to an assembly in a simulation I am running.

I get a segmentation violation when the /run/initialize command is given.

The traceback for the error is below:

#0  0x00007f638fc0c10c in waitpid () from /lib64/libc.so.6
#1  0x00007f638fb89de2 in do_system () from /lib64/libc.so.6
#2  0x00007f639a81c94f in TUnixSystem::StackTrace (this=0x25da170) at /home/jgallant/Desktop/ROOT/root-6.12.06/core/unix/src/TUnixSystem.cxx:2412
#3  0x00007f639a81f07c in TUnixSystem::DispatchSignals (this=0x25da170, sig=kSigSegmentationViolation) at /home/jgallant/Desktop/ROOT/root-6.12.06/core/unix/src/TUnixSystem.cxx:3643
#4  <signal handler called>
#5  0x00007f63915f6dcd in G4AssemblyVolume::MakeImprint(G4AssemblyVolume*, G4LogicalVolume*, HepGeom::Transform3D&, int, bool) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4geometry.so
#6  0x00007f63915f7ba0 in G4AssemblyVolume::MakeImprint(G4LogicalVolume*, CLHEP::Hep3Vector&, CLHEP::HepRotation*, int, bool) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4geometry.so
#7  0x000000000040db72 in DetectorConstruction::SetupGeometry() ()
#8  0x000000000040e1e1 in DetectorConstruction::Construct() ()
#9  0x00007f63949ce5b8 in G4RunManager::InitializeGeometry() () from /home/jgallant/Desktop/Geant4/install/lib64/libG4run.so
#10 0x00007f63949ce4ea in G4RunManager::Initialize() () from /home/jgallant/Desktop/Geant4/install/lib64/libG4run.so
#11 0x00007f63949e8748 in G4RunMessenger::SetNewValue(G4UIcommand*, G4String) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4run.so
#12 0x00007f6390c5c53f in G4UIcommand::DoIt(G4String) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#13 0x00007f6390c795a3 in G4UImanager::ApplyCommand(char const*) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#14 0x00007f6390c49a37 in G4UIbatch::ExecCommand(G4String const&) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#15 0x00007f6390c4b0fb in G4UIbatch::SessionStart() () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#16 0x00007f6390c70a33 in G4UImanager::ExecuteMacroFile(char const*) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#17 0x00007f6390c64df5 in G4UIcontrolMessenger::SetNewValue(G4UIcommand*, G4String) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#18 0x00007f6390c5c53f in G4UIcommand::DoIt(G4String) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#19 0x00007f6390c795a3 in G4UImanager::ApplyCommand(char const*) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4intercoms.so
#20 0x00007f639b8718ca in G4UIterminal::ExecuteCommand(G4String const&) () from /home/jgallant/Desktop/Geant4/install/lib64/libG4interfaces.so
#21 0x00007f639b872ea4 in G4UIterminal::SessionStart() () from /home/jgallant/Desktop/Geant4/install/lib64/libG4interfaces.so
#22 0x000000000040987a in main ()

Commenting out the new volumes does not solve the solution, nor does commenting out any old volumes. I am not as proficient as I would like to be with C++ and as such I am having trouble interpreting the issue.

Any help would be greatly appreciated.

Thanks,

Jack

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: Segmentation Violation issue   (Jack Gallant - 04 Jun, 2018)
 Add Message Add Message
to: "Segmentation Violation issue"

 Subscribe Subscribe

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


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]