Problem 594 - Hadron lists
Summary: Hadron lists
Status: RESOLVED WORKSFORME
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic (show other problems)
Version: 6.0
Hardware: PC Linux
: P1 critical
Assignee: Hans-Peter.Wellisch
URL: http://meco.ps.uci.edu/~tumakov/tmp/N04
Depends on:
Blocks:
 
Reported: 2004-02-27 12:56 CET by tumakov
Modified: 2004-03-04 07:35 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description tumakov 2004-02-27 12:56:53 CET
I worked with provided hadron lists successfully earlier.
Now I have geant6.0p1 installed.

If I use PhysicsLists in my application from exampleN04, it works.
with PhysicsLists from geant4/hadron_lists it doesn't.

To simplify the problem I'll tried to run PhysicsLists from geant4/hadron_lists
in exampleN04 itself and got the same problem.

The only change I made - add
#include "QGSC.hh"
changed
 //  runManager->SetUserInitialization(new ExN04PhysicsList);
into
  runManager->SetUserInitialization(new QGSC);     // QGSC
add
include hadronic_lists.gmk
into GNUmakefile from composite_calorimeter example

This modified N04 example one can find in the provided URL.

Full problem report is there in the file N04/problem.txt

Partually the message of this  run-time error I give below.
Can somebody suggest what is missing?

Best regards, Vladimir Tumakov


Start Run processing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1078320512 (LWP 3526)]
0x082e7d91 in __normal_iterator (this=0xbfffc728, __i=@0x4) at stl_iterator.h:584
(xxgdb) info stack
#0  0x082e7d91 in __normal_iterator (this=0xbfffc728, __i=@0x4) at
stl_iterator.h:584
#1  0x082e7758 in std::vector<G4PhysicsVector*, std::allocator<G4PhysicsVector*>
>::begin() (this=0x4) at stl_vector.h:208
#2  0x082e793e in std::vector<G4PhysicsVector*,
std::allocator<G4PhysicsVector*>>::operator[](unsigned) (this=0x4, __n=0) at
stl_vector.h:289
#3  0x082e8f17 in G4VEnergyLossProcess::GetMeanFreePath(G4Track const&, double,
G4ForceCondition*) (this=0x89737f4, track=@0x88a9a50, cond=0x88be870) at
G4VEnergyLossProcess.hh:483
#4  0x082e88c6 in
G4VContinuousDiscreteProcess::PostStepGetPhysicalInteractionLength(G4Track
const&, double, G4ForceCondition*) (this=0x89737f4, track=@0x88a9a50,
previousStepSize=0, condition=0x88be870) at G4VContinuousDiscreteProcess.hh:162
#5  0x083b07a2 in G4VProcess::PostStepGPIL(G4Track const&, double,
G4ForceCondition*) (this=0x89737f4, track=@0x88a9a50, previousStepSize=0,
condition=0x88be870) at G4VProcess.hh:417
Comment 1 tumakov 2004-02-27 17:20:59 CET
I solved the problem myself.
The reson was that during geant4 compilation there were several subroutines
with compillations errors with diagnostics of internal bugs
which disappeared when I tried to recompile them again.

Regards, Vladimir
Comment 2 Hans-Peter.Wellisch 2004-03-04 07:35:59 CET
Phew...