Message: segmentation fault probably related to G4NeutronHPFSFissionFS::ApplyYourself (using geant4.9.3) Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Sad segmentation fault probably related to G4NeutronHPFSFissionFS::ApplyYourself (using geant4.9.3) 

Forum: Installation and Configuration
Date: 22 Mar, 2010
From: Cristian Bungau <Cristian Bungau>

Hi,

My run stops with a segmentation fault if I'm using a HP physics list, so I guess something is not configured/installed correctly:

This is the output I get:

---> Begin of event: 0

--------- Ranecu engine status ---------
 Initial seed (index) = 0
 Current couple of seeds = 481572697, 867673556
----------------------------------------
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
0x0012d422 in __kernel_vsyscall ()
(gdb) backtrace
#0  0x0012d422 in __kernel_vsyscall ()
#1  0x05b1b4d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0x05b1e932 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0x05a844df in __gnu_cxx::__verbose_terminate_handler() ()
   from /usr/lib/libstdc++.so.6
#4  0x05a82415 in ?? () from /usr/lib/libstdc++.so.6
#5  0x05a82452 in std::terminate() () from /usr/lib/libstdc++.so.6
#6  0x05a82591 in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x05a82c0f in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#8  0x05a82ced in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
#9  0x01f4bdb2 in G4AllocatorPool::Grow() ()
   from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4globman.so
#10 0x00da9e9e in G4NeutronHPFSFissionFS::ApplyYourself(int, int, double*) ()
   from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4had_neu_hp.so
#11 0x00db61fe in G4NeutronHPFissionFS::ApplyYourself(G4HadProjectile const&)
    () from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4had_neu_hp.so
#12 0x00d941f5 in G4NeutronHPChannel::ApplyYourself(G4HadProjectile const&, int) () from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4had_neu_hp.so
#13 0x00dafacb in G4NeutronHPFission::ApplyYourself(G4HadProjectile const&, G4Nucleus&) ()
   from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4had_neu_hp.so
#14 0x00b356b2 in G4HadronicProcess::PostStepDoIt(G4Track const&, G4Step const&) () from /home/cristian/geant4/geant4.9.3/lib/Linux-g++/libG4hadronic_mgt.so
---Type <return> to continue, or q <return> to quit---

I should probably use the Hadronic Physics list forum, but I've seen they don't deal with segmentation faults there. I would be very grateful for any suggestions.

Thank you,

Cristian

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

1 None: Re: segmentation fault probably related to G4NeutronHPFSFissionFS::ApplyYourself (using geant4.9.3)   (Quentin Cherel - 24 Mar, 2010)
(_ None: Re: segmentation fault probably related to G4NeutronHPFSFissionFS::ApplyYourself (using geant4.9.3)   (Cristian Bungau - 07 Apr, 2010)
 Add Message Add Message
to: "segmentation fault probably related to G4NeutronHPFSFissionFS::ApplyYourself (using geant4.9.3)"

 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 ]