Message: Re: Problem with G4SteppingManager::Stepping():DefinePhysicalStepLength() Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Problem with G4SteppingManager::Stepping():DefinePhysicalStepLength() 

Forum: Event and Track Management
Re: Question Problem with G4SteppingManager::Stepping():DefinePhysicalStepLength() (Yapeng Zhang)
Date: 10 Apr, 2008
From: Vladimir IVANTCHENKO <vnivanch@mail.cern.ch>

On Wed, 9 Apr 2008, Yapeng Zhang wrote:

> *** Discussion title: Event and Track Management
> Email replies to PublicHyperNews@slac.stanford.edu must include:
>   In-Reply-To: <"/eventtrackmanage/785"@geant4-hn.slac.stanford.edu>
>   Subject: ...change this to be about your reply.
> 
> Hi, everybody,
> 
> I use Geant4.8.1.p02 with gcc 3.4.3, CLHEP 1.9.2.3 and the GDML_2_9_0.
> There is no error in compiling process. I can get a proper geometric structure of detector in both OGLIX and Wired environment. 
> But when I run the command "/run/beamOn 1" in Idle state, I get the following crash messages. 
> Then, I found the crash point is  at "G4SteppingManager::Stepping():DefinePhysicalStepLength()".
> The following is the values of some private variables of G4SteppingManager class before runing the Stepping():DefinePhysicalStepLength()function,  
> "physIntLength  1.79769e+308,  fCondition  7117256, fGPIlSelection  536870912".
> ------------------------------------------------------------------------------------
>  *** Break *** segmentation violation
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> Attaching to program: /proc/28761/exe, process 28761
> [Thread debugging using libthread_db enabled]
> [New Thread 2305843009367821664 (LWP 28761)]
> 0xa000000000010641 in ?? ()
> #1  0x20000000090c4eb0 in waitpid () from /lib/tls/libc.so.6.1
> #2  0x2000000009013810 in do_system () from /lib/tls/libc.so.6.1
> #3  0x200000000149c6c0 in TUnixSystem::Exec () from /cern/root/lib/libCore.so
> #4  0x20000000014a9da0 in TUnixSystem::StackTrace ()
>    from /cern/root/lib/libCore.so
> #5  0x20000000014a2390 in TUnixSystem::DispatchSignals ()
>    from /cern/root/lib/libCore.so
> #6  0x20000000014a2700 in SigHandler () from /cern/root/lib/libCore.so
> #7  0x20000000014a01a0 in sighandler () from /cern/root/lib/libCore.so
> #8  <signal handler called>
> #9  0x20000000052ec410 in G4VEnergyLossProcess::GetMeanFreePath ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4muons.so
> #10 0x20000000052e2c80 in G4VContinuousDiscreteProcess::PostStepGetPhysicalInter
> actionLength () from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4muons.so
> #11 0x2000000007529200 in G4SteppingManager::DefinePhysicalStepLength ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4tracking.so
> #12 0x2000000004c4cef0 in G4SteppingManager::Stepping ()
>    from /home/ypzhang/geant4/HplusLib/Linux-g++/libHplus.so
> #13 0x2000000004c50d30 in G4TrackingManager::ProcessOneTrack ()
>    from /home/ypzhang/geant4/HplusLib/Linux-g++/libHplus.so
> #14 0x200000000745d310 in G4EventManager::DoProcessing ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4event.so
> #15 0x200000000745de90 in G4EventManager::ProcessOneEvent ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4event.so
> #16 0x2000000004c44640 in G4RunManager::DoEventLoop ()
>    from /home/ypzhang/geant4/HplusLib/Linux-g++/libHplus.so
> #17 0x2000000004c41710 in G4RunManager::BeamOn ()
>    from /home/ypzhang/geant4/HplusLib/Linux-g++/libHplus.so
> #18 0x2000000006e3ea90 in G4RunMessenger::SetNewValue ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4run.so
> #19 0x2000000007e03280 in G4UIcommand::DoIt ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4intercoms.so
> #20 0x2000000007e1fd10 in G4UImanager::ApplyCommand ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4intercoms.so
> #21 0x2000000007e203c0 in G4UImanager::ApplyCommand ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4intercoms.so
> #22 0x20000000055dea40 in G4UIterminal::ExecuteCommand ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4UIbasic.so
> #23 0x20000000055e1560 in G4UIterminal::SessionStart ()
>    from /cern/geant4/geant4.8.1.p02/lib/Linux-g++/libG4UIbasic.so
> #24 0x4000000000003a70 in main ()
> WARNING - Attempt to delete the physical volume store while geometry closed !
> WARNING - Attempt to delete the logical volume store while geometry closed !
> WARNING - Attempt to delete the solid store while geometry closed !
> WARNING - Attempt to delete the region store while geometry closed !
> ------------------------------------------------------------------------------
> Any advice would be greatly appreciated.
> 
> Thans a lot!
> 
> Yapeng Zhang
> 

Hello Yapeng,

This code have been tested on a very high statistic, so we can exclude G4 
bug in a place which is called at every step of a particle.

To debug your problem I would suggest to activate verbosity. At least,
"/tracking/verbose 2" but may be more detailed verbosity.

I hope you are using one of the reference Physics Lists.

VI
 

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

 Add Message Add Message
to: "Re: Problem with G4SteppingManager::Stepping():DefinePhysicalStepLength()"

 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 ]