I have the same problem as described in bug #745: my system is SuSe Linux with gcc 3.3.3: ychen@droplet:~> gcc -v Reading specs from /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib64 --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit x86_64-suse-linux Thread model: posix gcc version 3.3.3 (SuSE Linux) This system runs ok with Geant4 5.2. but recently when I upgrade it to Geant4 7.0.p01, there was no error or warning with compilinh and link with examples and the problem occured when running e.g. N01: >gdb ./bin/Linux-g++/exampleN01 GNU gdb 5.3.92 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-suse-linux"... (gdb) run Starting program: /storage/home/ychen/MonteCarloSimulator/geant4.7.0.p01/examples/novice/N01/bin/Linux-g++/exampleN01 ************************************************************* Geant4 version $Name: geant4-07-00-patch-01 $ (23-February-2005) Copyright : Geant4 Collaboration Reference : NIM A 506 (2003), 250-303 WWW : http://cern.ch/geant4 ************************************************************* G4VUserPhysicsList::BuildPhysicsTable does not retrieve Cut Table but calculate ========= Table of registered couples ============================== Index : 0 used in the geometry : Yes recalculation needed : No Material : ArgonGas Range cuts : gamma 1 mm e- 1 mm e+ 1 mm Energy thresholds : gamma 990 eV e- 990 eV e+ 990 eV Region(s) which use this couple : DefaultRegionForTheWorld Index : 1 used in the geometry : Yes recalculation needed : No Material : Aluminum Range cuts : gamma 1 mm e- 1 mm e+ 1 mm Energy thresholds : gamma 6.88731 keV e- 596.68 keV e+ 568.011 keV Region(s) which use this couple : DefaultRegionForTheWorld Index : 2 used in the geometry : Yes recalculation needed : No Material : Lead Range cuts : gamma 1 mm e- 1 mm e+ 1 mm Energy thresholds : gamma 100.511 keV e- 1.37814 MeV e+ 1.28002 MeV Region(s) which use this couple : DefaultRegionForTheWorld ==================================================================== Start Run processing. ===================================== G4EventManager::ProcessOneEvent() ===================================== 1 primaries are passed from G4EventTransformer. !!!!!!! Now start processing an event !!!!!!! ### pop requested out of 1 stacked tracks. ********************************************************************************************************* * G4Track Information: Particle = geantino, Track ID = 1, Parent ID = 0 ********************************************************************************************************* Program received signal SIGSEGV, Segmentation fault. 0x000000000047e069 in G4NavigationHistory::NewLevel(G4VPhysicalVolume*, EVolume, int) () (gdb) where #0 0x000000000047e069 in G4NavigationHistory::NewLevel(G4VPhysicalVolume*, EVolume, int) () #1 0x000000000047e50f in G4VoxelNavigation::LevelLocate(G4NavigationHistory&, G4VPhysicalVolume const*, int, Hep3Vector const&, Hep3Vector const*, bool, Hep3Vector&) () #2 0x000000000047c646 in G4Navigator::LocateGlobalPointAndSetup(Hep3Vector const&, Hep3Vector const*, bool, bool) () #3 0x000000000042c575 in G4SteppingManager::SetInitialStep(G4Track*) () #4 0x0000000000422d71 in G4TrackingManager::ProcessOneTrack(G4Track*) () #5 0x00000000004180e2 in G4EventManager::DoProcessing(G4Event*) () #6 0x000000000040a25a in G4RunManager::DoEventLoop(int, char const*, int) () #7 0x000000000040893a in G4RunManager::BeamOn(int, char const*, int) () #8 0x0000000000404c50 in main () (gdb) In bug#745, there is a link for solution, but I cannot see that page as I go to Geant User Forum: The connetion was refused when attempting to contact geant4-hn.slac.stanford.edu:5090 Can someone email me that solution or put it on an easy-accessable webpage? Thanks, Yu Chen
Please update to Geant4 7.1. 7.0.p01 and previous versions are not tested on 64-bits architectures.
Thanks fro reply. But my problem is that I have to stick on Geant4 7.0.p01 since Geant4 7.1 is not supported by GATE and there is some reported problem with Geant4 7.1 while installing GATE. My goal is running GATE with Geant4 7.0.p01 in that 64 bits cluster. I believe with a temporary solution I can achieve it. Of course, in the future, when GATE uses newer Geant4 version, this problem could be completely solved. Please tell me how to do with Geant4 7.0.p01. Thanks, Yu Chen, Ph.D. University of Massachusetts Medical School Division of Nuclear Medicine 55 Lake Avenue North Worcester, MA 01655-0243 Phone: (508) 856-6123 Fax: (508) 856-4572
You can try to compile the module of geometry/volumes in debug mode (G4DEBUG=1) and see if that can help. No guarantees, though.
Thanks again. I tried to complile geometry/volumes module with G4DEBUG=1, but it didn't help. Finally I solve the problem by doing the following: adding a line in the $G4INSTALL/config/sys/Linux-g++.gmk: CXXFLAGS += -mcpu=k8 -msse2 By the way, if you want to vis module installed, you should replace /usr/X11R6/lib with /usr/X11R6/lib64 $(OGLHOME)/lib with $(OGLHOME)/lib64 Yu Chen
