1 | <!-- ******************************************************** --> |
---|
2 | <!-- --> |
---|
3 | <!-- [History] --> |
---|
4 | <!-- 1st version created: Katsuya Amako, Dec-2006 --> |
---|
5 | <!-- --> |
---|
6 | <!-- ******************************************************** --> |
---|
7 | |
---|
8 | |
---|
9 | <!-- ********************* QandA Section ******************** --> |
---|
10 | <section id="qanda.RunTimeProb"> |
---|
11 | <title> |
---|
12 | Run Time Problems |
---|
13 | </title> |
---|
14 | |
---|
15 | <qandaset defaultlabel="qanda"> |
---|
16 | |
---|
17 | <!-- ******* QandA Entry ******** --> |
---|
18 | <qandaentry id="qanda.RunTimeProb.SegFltInExmp"> |
---|
19 | |
---|
20 | <question><para> |
---|
21 | On Linux, I get a segmentation fault as soon as I run one of the official |
---|
22 | examples. |
---|
23 | </para></question> |
---|
24 | |
---|
25 | <answer><para> |
---|
26 | Check that the CLHEP library has been installed and compiled coherently |
---|
27 | with the same compiler you use for installing Geant4 and for the same |
---|
28 | version of Linux distribution. For example, a binary object produced with |
---|
29 | Red-Hat 7.X is not fully compatible with binaries running on RH 9.X or |
---|
30 | higher, due to different libc used in the two configurations. |
---|
31 | </para></answer> |
---|
32 | |
---|
33 | </qandaentry> |
---|
34 | |
---|
35 | |
---|
36 | <!-- ******* QandA Entry ******** --> |
---|
37 | <qandaentry id="qanda.RunTimeProb.ErrShareLib"> |
---|
38 | |
---|
39 | <question><para> |
---|
40 | I installed Geant4 libraries and built my application, when I try to run |
---|
41 | it I get: |
---|
42 | <informalexample><programlisting> |
---|
43 | error in loading shared libraries: |
---|
44 | libCLHEP.so: cannot open shared object file: |
---|
45 | No such file or directory. |
---|
46 | </programlisting></informalexample> |
---|
47 | </para></question> |
---|
48 | |
---|
49 | <answer><para> |
---|
50 | Your installation of CLHEP includes shared libraries. You need to specify |
---|
51 | the path where libCLHEP.so is installed through your environment variable |
---|
52 | <literal>LD_LIBRARY_PATH</literal>. For example, in tcsh UNIX shell: |
---|
53 | <informalexample><programlisting> |
---|
54 | setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$CLHEP_BASE_DIR/lib |
---|
55 | </programlisting></informalexample> |
---|
56 | </para></answer> |
---|
57 | |
---|
58 | </qandaentry> |
---|
59 | |
---|
60 | |
---|
61 | <!-- ******* QandA Entry ******** --> |
---|
62 | <qandaentry id="qanda.RunTimeProb.errFPE"> |
---|
63 | |
---|
64 | <question><para> |
---|
65 | On my system I get a Floating Point Exception (FPE) since some physics |
---|
66 | processes sometimes return <literal>DBL_MAX</literal> as interaction |
---|
67 | length and this number is afterwards multiplied by a number greater |
---|
68 | than 1. |
---|
69 | </para></question> |
---|
70 | |
---|
71 | <answer><para> |
---|
72 | Geant4 coding conventions and installation setup explicitly follow the |
---|
73 | ANSI/IEEE-754 Standard for the initialization of floating-point |
---|
74 | arithmetic hardware and portability. The Standard foresees floating-point |
---|
75 | arithmetic to be nonstop and underflows to be gradual. On DEC platforms, |
---|
76 | for example, the ANSI/IEEE-754 Standard compliance needs to be explicitly |
---|
77 | set (since deactivated by default); in this case we use infact the option |
---|
78 | "-ieee" on the DEC/cxx native C++ compiler to achieve this. You should |
---|
79 | check if your compiler provides compilation options for activating Standard |
---|
80 | initialization of FP arithmetic (it may be platform specific). |
---|
81 | </para></answer> |
---|
82 | |
---|
83 | </qandaentry> |
---|
84 | |
---|
85 | |
---|
86 | |
---|
87 | </qandaset> |
---|
88 | </section> |
---|