Problem 733 - segmentation violation in extended example exgps
Summary: segmentation violation in extended example exgps
Status: RESOLVED INVALID
Alias: None
Product: Examples/Extended
Classification: Unclassified
Component: eventgenerator/exgps (show other problems)
Version: 7.0
Hardware: All Linux
: P2 normal
Assignee: Fan.Lei
URL:
Depends on:
Blocks:
 
Reported: 2005-03-24 07:46 CET by chipaux
Modified: 2007-04-08 18:59 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description chipaux 2005-03-24 07:46:46 CET
A segmentation violation break occurs in extended example exgps when executing
the command run/beamOn in macro "exgps.in".
G4 version : 7.0,
AIDA version : 3.2.1 (AIDAJNI 3.2.1.2)
version gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5)

The same environment works perfectly for extended example A01.

Here are the output :

$G4EXE/exGPS exgps.in

*************************************************************
 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
*************************************************************

Visualization Manager instantiating...
Visualization Manager initialising...
Registering graphics systems...

You have successfully chosen to use the following graphics systems.
Current available graphics systems are:
  DAWNFILE (DAWNFILE)
  VRML1FILE (VRML1FILE)
  VRML2FILE (VRML2FILE)
  RayTracer (RayTracer)
Verbosity Set to: 0
1 VRML2FILE scene handlers extanct.
WARNING: objects with visibility flag set to "false" will not be drawn!
  "/vis/viewer/set/culling global false" to Draw such objects.
  Also see other "/vis/viewer/set" commands.
WARNING: For systems which are not "auto-refresh" you will need to
  issue "/vis/viewer/refresh" or "/vis/viewer/flush".
G4VUserPhysicsList::BuildPhysicsTable does not retrieve Cut Table but calculate
### Run 0 start.
Loaded linked in JVM.

---> Begin of event: 0

*** Break *** segmentation violation
 Generating stack trace...
 0x41973ce3 in JVM_handle_linux_signal + 0x513
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x41972b18 in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x41c07610 in <unknown> from /lib/tls/libpthread.so.0
 0x44035dc4 in <unknown function>
 0x44035e9b in <unknown function>
 0x44035e9b in <unknown function>
 0x440361a1 in <unknown function>
 0x440331c4 in <unknown function>
 0x418be6e4 in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x4197279d in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x418be936 in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x418c7137 in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x418cca46 in <unknown>
from /home/daplxa177/mnt/chipaux/JDK/j2sdk1.4.2_06/jre/lib/i386/client/libjvm.so
 0x41678ff4 in JNIEnv_::CallVoidMethod(_jobject*, _jmethodID*, ...) + 0x1c
from /home/daplxa177/mnt/chipaux/Aida/Aidajni/3.2.1.2/lib/Linux-
g++/libAIDAJNI.so
 0x416d4ad9 in JAIDA::JITuple::fill(int, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&) + 0x3f
from /home/daplxa177/mnt/chipaux/Aida/Aidajni/3.2.1.2/lib/Linux-
g++/libAIDAJNI.so
 0x416d7631 in virtual thunk [v:0,-60] to JAIDA::JITuple::fill(int,
std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
+ 0x27 from /home/daplxa177/mnt/chipaux/Aida/Aidajni/3.2.1.2/lib/Linux-
g++/libAIDAJNI.so
 0x080b9b7d in exGPSAnalysisManager::Fill(G4String, double, double, double,
double, double, double, double) + 0x165
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x080bc43d in exGPSEventAction::EndOfEventAction(G4Event const*) + 0x601
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x0813da44 in G4EventManager::DoProcessing(G4Event*) + 0x728
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x0812b3f5 in G4RunManager::DoEventLoop(int, char const*, int) + 0xc5
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x0812aeb4 in G4RunManager::BeamOn(int, char const*, int) + 0x44
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x08133e2f in G4RunMessenger::SetNewValue(G4UIcommand*, G4String) + 0x78f
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x08296778 in G4UIcommand::DoIt(G4String) + 0xd0
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x082a412e in G4UImanager::ApplyCommand(char const*) + 0x522
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x082acc9e in G4UIbatch::SessionStart() + 0x1fe
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x082a23c9 in G4UImanager::ExecuteMacroFile(char const*) + 0x31
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x082b1907 in G4UIcontrolMessenger::SetNewValue(G4UIcommand*, G4String) +
0x2b3 from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x08296778 in G4UIcommand::DoIt(G4String) + 0xd0
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x082a412e in G4UImanager::ApplyCommand(char const*) + 0x522
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x080b8e37 in main + 0x1e3
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
 0x42015574 in __libc_start_main + 0xe4 from /lib/tls/libc.so.6
 0x080b8bc5 in HepRotation::phiZ() const + 0x41
from /home/daplxa177/mnt/chipaux/Geant4/geant4.7.0.p01/bin/Linux-g++/exGPS
Abandon (core dumped)
Comment 1 flei 2005-04-04 03:50:59 CEST
This is likely due to a bug, AIDAJNI-44, in AIDAJNI which has been fixed in
version 3.2.3. So please try the example with newer version of AIDA/JAIDA and
see if the problem persists.
Comment 2 chipaux 2005-04-04 09:31:59 CEST
That's right, this problem does not appear using AIDAJNI 3.2.3.

Thanks !