Message: Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005 Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005 

Keywords: Hadronic, VC++8
Forum: Documentation and Examples
Re: None Hadronic physics problems in examples under WinXP/Cygwin/VS2005 (David Shipley)
Re: Question Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005 (Gabriele Cosmo)
Re: None Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005 (David Shipley)
Re: More Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005 (Gabriele Cosmo)
Date: 11 Aug, 2006
From: David Shipley <David Shipley>

Gabriele,

> in order to have the complete information with line numbers, you need
>  to compile the G4 libraries in debug-mode (i.e. G4DEBUG set in your
> environment before compiling and building the libraries). To retrieve
> the dump trace you need to launch the debug process in Visual Studio
> when asked, and eventually ask to print the trace of the crash, if it
> does not appear already automatically. I don't have VS2005 at hand, but
> I guess the behavior is similar to VS2003...

I've recompiled the Geant4 kernel libraries and TestEm7 with G4DEBUG=1 as suggested. I then executed TestEm7 with the macro file proton.mac with only 2 changes (1000 events & binary hadronic physics enabled).

Here is the call stack produced by VS2005 at the point at which the program results in an unhandled win32 exception (during the first event).

        msvcr80.dll!_crt_debugger_hook(int _Reserved=)  Line 65 C
        msvcr80.dll!_invoke_watson(const wchar_t * pszExpression=0x00000000, const wchar_t * pszFunction=0x00000000, const wchar_t * pszFile=0x00000000, unsigned int nLine=0, unsigned int pReserved=0)  Line 181 + 0x7 bytes  C++
        msvcr80.dll!_invalid_parameter_noinfo()  Line 99 + 0xc bytes    C++
        TestEm7.exe!std::vector<CLHEP::Hep3Vector,std::allocator<CLHEP::Hep3Vector> >::operator[](unsigned int _Pos=0)  Line 762        C++
        TestEm7.exe!G4Fancy3DNucleus::ChoosePositions()  Line 313 + 0x13 bytes  C++
        TestEm7.exe!G4Fancy3DNucleus::Init(double theA=16.000000000000000, double theZ=8.0000000000000000)  Line 95     C++
        TestEm7.exe!G4BinaryCascade::ApplyYourself(const G4HadProjectile & aTrack={...}, G4Nucleus & aNucleus={...})  Line 158  C++
        TestEm7.exe!G4HadronicInteractionWrapper::ApplyInteraction(G4HadProjectile & thePro={...}, G4Nucleus & targetNucleus={...}, G4HadronicInteraction * theInteraction=0x01682f38)  Line 37 C++
        TestEm7.exe!G4HadronicProcess::GeneralPostStepDoIt(const G4Track & aTrack={...}, const G4Step & __formal={...})  Line 418 + 0x2b bytes  C++
        TestEm7.exe!G4HadronInelasticProcess::PostStepDoIt(const G4Track & aTrack={...}, const G4Step & aStep={...})  Line 81   C++
        TestEm7.exe!G4SteppingManager::InvokePSDIP(unsigned int np=3)  Line 503 + 0x21 bytes    C++
        TestEm7.exe!G4SteppingManager::InvokePostStepDoItProcs()  Line 485      C++
        TestEm7.exe!G4SteppingManager::Stepping()  Line 208     C++
        TestEm7.exe!G4TrackingManager::ProcessOneTrack(G4Track * apValueG4Track=0x0178bed0)  Line 120 + 0xb bytes       C++
        TestEm7.exe!G4EventManager::DoProcessing(G4Event * anEvent=0x018bfa88)  Line 178        C++
        TestEm7.exe!G4EventManager::ProcessOneEvent(G4Event * anEvent=0x018bfa88)  Line 328     C++
        TestEm7.exe!G4RunManager::DoEventLoop(int n_event=1000, const char * macroFile=0x00000000, int n_select=-1)  Line 233   C++
        TestEm7.exe!G4RunManager::BeamOn(int n_event=1000, const char * macroFile=0x00000000, int n_select=-1)  Line 137        C++
        TestEm7.exe!G4RunMessenger::SetNewValue(G4UIcommand * command=0x01578c48, G4String newValue={...})  Line 255    C++
        TestEm7.exe!G4UIcommand::DoIt(G4String parameterList={...})  Line 211   C++
        TestEm7.exe!G4UImanager::ApplyCommand(const char * aCmd=0x0012f71c)  Line 399 + 0x25 bytes      C++
        TestEm7.exe!G4UIbatch::SessionStart()  Line 92 + 0x15 bytes     C++
        TestEm7.exe!G4UImanager::ExecuteMacroFile(const char * fileName=0x0012f8a8)  Line 222 + 0x13 bytes      C++
        TestEm7.exe!G4UIcontrolMessenger::SetNewValue(G4UIcommand * command=0x01568320, G4String newValue={...})  Line 177      C++
        TestEm7.exe!G4UIcommand::DoIt(G4String parameterList={...})  Line 211   C++
        TestEm7.exe!G4UImanager::ApplyCommand(const char * aCmd=0x016039b8)  Line 399 + 0x25 bytes      C++
        TestEm7.exe!G4UImanager::ApplyCommand(G4String aCmd={...})  Line 343 + 0x11 bytes       C++

I also recompiled CLHEP without using '/D_SECURE_SCL=0' and installed these libraries (ignoring the test failures). Executing TestEm7 again with the same macro file produced the same trace output. It therefore seems that the use of '/D_SECURE_SCL=0' during the compilation of CLHEP is not contributing to the failure.

I will look into this further but do you have any suggestions so far?

David.

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

1 None: Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005   (David Shipley - 11 Aug, 2006)
3 Feedback: Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005   (Gabriele Cosmo - 11 Aug, 2006)
1 Note: Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005   (David Shipley - 30 Aug, 2006)
 Add Message Add Message
to: "Re: Hadronic physics problems in examples under WinXP/Cygwin/VS2005"

 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 ]