Message: Segfault Using Geant4 10.01 & QGSP_BERT_HP Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Segfault Using Geant4 10.01 & QGSP_BERT_HP  

Forum: Hadronic Processes
Date: 22 Jan, 2015
From: Nikos Karastathis <Nikos Karastathis>

Hi all,

I am implementing the QGSP_BERT_HP physics list in my project as

   G4PhysListFactory factory;
    G4VModularPhysicsList *physics = 0;
    G4String physName = "QGSP_BERT_HP";
    physics = factory.GetReferencePhysList(physName);
    runManager->SetUserInitialization(physics);

and it seems that under the new version this resolves to a segfault when the program exits. Is this a known issue? I've seen similar issues with other reference lists. Any insight on how this can be addressed?

Best regards N.

************************************************************
 Geant4 version Name: geant4-10-01    (5-December-2014)
                      Copyright : Geant4 Collaboration
                      Reference : NIM A 506 (2003), 250-303
                            WWW : http://cern.ch/geant4
*************************************************************

G4PhysListFactory::GetReferencePhysList <QGSP_BERT_HP> EMoption= 0 <<< Geant4 Physics List simulation engine: QGSP_BERT_HP 3.0

<<< Reference Physics List QGSP_BERT_HP is built

Creating SD with name: /mydet/UMSD Total navigation history collections cleaned: 2

 *** Break *** segmentation violation

=========================================================== There was a crash. This is the entire stack trace of all threads: ===========================================================

Thread 2 (process 21851):

#0  0x00007fff8e4d9662 in kevent64 ()
#1  0x00007fff8ec2e421 in _dispatch_mgr_invoke ()
#2  0x00007fff8ec2e136 in _dispatch_mgr_thread ()

Thread 1 (process 21851):

#0  0x00007fff8e4d8e38 in wait4 ()
#1  0x00007fff8f30b090 in system ()
#2  0x000000010896d1db in TUnixSystem::StackTrace ()
#3  0x000000010896ae64 in TUnixSystem::DispatchSignals ()
#4  <signal handler called>
#5  0x00000001073d2a3f in G4NeutronHPInelastic::~G4NeutronHPInelastic ()
#6  0x00000001073d2f8f in G4NeutronHPInelastic::~G4NeutronHPInelastic ()
#7  0x00000001073980a7 in G4HadronicInteractionRegistry::Clean ()
#8  0x000000010708e4ef in G4HadronicProcessStore::~G4HadronicProcessStore ()
#9  0x0000000107092eb4 in G4ThreadLocalSingleton<G4HadronicProcessStore>::Clear ()
#10 0x0000000107092d81 in G4ThreadLocalSingleton<G4HadronicProcessStore>::~G4ThreadLocalSingleton ()
#11 0x00007fff8f2ec7a1 in __cxa_finalize ()
#12 0x00007fff8f2eca4c in exit ()
#13 0x00007fff89f01604 in start ()
===========================================================

The lines below might hint at the cause of the crash. If they do not help you then please submit a bug report at http://root.cern.ch/bugs. Please post the ENTIRE stack trace from above as an attachment in addition to anything else that might help us fixing this issue. ===========================================================

#5  0x00000001073d2a3f in G4NeutronHPInelastic::~G4NeutronHPInelastic ()
#6  0x00000001073d2f8f in G4NeutronHPInelastic::~G4NeutronHPInelastic ()
#7  0x00000001073980a7 in G4HadronicInteractionRegistry::Clean ()
#8  0x000000010708e4ef in G4HadronicProcessStore::~G4HadronicProcessStore ()
#9  0x0000000107092eb4 in G4ThreadLocalSingleton<G4HadronicProcessStore>::Clear ()
#10 0x0000000107092d81 in G4ThreadLocalSingleton<G4HadronicProcessStore>::~G4ThreadLocalSingleton ()
#11 0x00007fff8f2ec7a1 in __cxa_finalize ()
#12 0x00007fff8f2eca4c in exit ()
#13 0x00007fff89f01604 in start ()
===========================================================
#8  0x00000001096384ef in G4HadronicProcessStore::~G4HadronicProcessStore ()
#9  0x000000010963ceb4 in G4ThreadLocalSingleton<G4HadronicProcessStore>::Clear ()
#10 0x000000010963cd81 in G4ThreadLocalSingleton<G4HadronicProcessStore>::~G4ThreadLocalSingleton ()
#11 0x00007fff8f2ec7a1 in __cxa_finalize ()
#12 0x00007fff8f2eca4c in exit ()
#13 0x00007fff89f01604 in start ()
===========================================================

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

1 Idea: Re: Segfault Using Geant4 10.01 & QGSP_BERT_HP   (Vladimir Ivanchenko - 07 Feb, 2015)
 Add Message Add Message
to: "Segfault Using Geant4 10.01 & QGSP_BERT_HP "

 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 ]