Problem 738 - Problem in G4NavigationHistory with gcc 3.4.3
Summary: Problem in G4NavigationHistory with gcc 3.4.3
Status: CLOSED LATER
Alias: None
Product: Geant4
Classification: Unclassified
Component: config (show other problems)
Version: 7.0
Hardware: PC Linux
: P2 normal
Assignee: Gabriele Cosmo
URL:
: 745 (view as problem list)
Depends on:
Blocks:
 
Reported: 2005-04-05 06:31 CEST by toga
Modified: 2005-05-23 10:52 CEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description toga 2005-04-05 06:31:46 CEST 
I installed geant4.7.0.p01 and clhep 1.9.1.2. Installation had no problem, I
can excute the geant4 based program, but the program doesn't run due to the
problem in G4NavigationHistory.
All of the programs were compiled with gcc 3.4.3 in x86_64 environment.
(OS is CentOS4.)

The below is the message from debug program "gdb".

Program received signal SIGSEGV, Segmentation fault.
0x00000000006d1f4a in G4NavigationHistory::G4NavigationHistory ()
    at new_allocator.h:86
86            { ::operator delete(__p); }
Current language:  auto; currently c++

I have no idea to solve this problem.
Comment 1 Gabriele Cosmo 2005-04-05 09:25:59 CEST 
We cannot reproduce the reported problem, since we do not have yet means to
test on 64-bits architectures.
Geant4 is currently supported on 32-bits architectures. Installations on 64-bits
systems may require an ad-hoc configuration different from the current one used
for the standard Linux/g++ installation.
It may also point out a configuration problem with the installed compiler. One
thing that the user can try is to build the Geant4 application (and/or the
whole G4 libraries) in debug mode (G4DEBUG set) and see if the problem shows up
again.
Comment 2 Gabriele Cosmo 2005-04-05 10:11:59 CEST 
Yasuhiro Togano <toga@ne.rikkyo.ac.jp> writes:

> Thank you very much for your comment.
>
> OK, I will try to build the G4 applications in debug mode.
> I will report the result in a few days.
>
> As you commented, I think this problem is due to the gcc3.4.3.
> Using the gcc3.2.3, I didn't have any problem in 64-bit environment.
>
> The file new_allocator.h may be added from after releasing the 3.2.3
> because I cannot find this file in version 3.2.3.
Comment 3 toga 2005-04-25 04:57:59 CEST 
Sorry, I don't build the G4 in debug mode, yet.
Because the G4 is working well by using the 32bit compilation.

The problem was the G4NavigationHistory and it calls the operator at
new_allocator.h.
The function is called internally, and this means that the problem is due to
the gcc3.4.3.

Now Geant4 is not supported on the 64-bits architectures.
If you try to use G4 in 64-bit environment, you "should" compile them in 32-
bit mode.
Comment 4 Gabriele Cosmo 2005-05-23 10:42:59 CEST 
We could verify that Geant4 7.0.p01 runs successfully in optimised mode on an
AMD 64-bits system installed with SLC3 (gcc-3.2.3).
Tests were also successful if using gcc-3.4.3, installed on the same system as
alternate compiler (NOTE: configured with --disable-shared).
Comment 5 Gabriele Cosmo 2005-05-23 10:52:59 CEST 
*** Bug 745 has been marked as a duplicate of this bug. ***
*** 'Gabriele.Cosmo@cern.ch' will be responsible for bug 745. ***