[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: errors/seg-fault in hdgeant
Hi All,
We have seen this before and the common work-around is to set HADR
to 1 instead of the default 4. There were recent private e-mail
discussions with Richard and Sascha where it was agreed that we should
change the default setting of HADR in the repository control.in file to
1. I think i was supposed to do that, but never did until just now.
Sorry that I didn't follow up on this earlier. The repository now has
the change and you can either update from there or just change HADR to 1
yourself in you control.in file.
Regards,
-David
Beni Zihlmann wrote:
> Hi Mark,
> I used your control.in file runing hdgeant in debug mode but using the
> latest
> repository code. I do not see the geometry errors, however, I also get
> a segmentation
> fault as indicated below. It seems the segmentation fault happens in a
> geant routine.
> maybe the data it gets is corrupted according to the geant manual:*
> **CALL GMICAP * GMICAP
> <http://www.kph.uni-mainz.de/computing/docu/geant/Geant-HTML/node352.html#GMICAP>
> calls the MICAP routines to handle the low-energy
> interaction of neutrons. It writes the eventual secondaries to the
> GEANT stack. GMICAP
> <http://www.kph.uni-mainz.de/computing/docu/geant/Geant-HTML/node352.html#GMICAP>
>
> is called from GFMFIN
> <http://www.kph.uni-mainz.de/computing/docu/geant/Geant-HTML/node352.html#GFMFIN>.
>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1209014576 (LWP 4261)]
> 0x0831aaaf in gmicap_ ()
> (gdb) bt
> #0 0x0831aaaf in gmicap_ ()
> #1 0x0831942a in gfmfin_ ()
> #2 0x08061036 in guhadr_ () at guhadr.F:131
> #3 0x0871f919 in jumpt0_ ()
> #4 0x000000a3 in ?? ()
> #5 0x426c9445 in ?? ()
> #6 0xbf824558 in ?? ()
> #7 0x083d3e22 in gtneut_ ()
> #8 0x0838fd95 in gtrack_ ()
> #9 0x0831850f in gutrak_ ()
> #10 0x0871f919 in jumpt0_ ()
> #11 0x60000000 in ?? ()
> #12 0x3f87a2a8 in ?? ()
> #13 0xbf824878 in ?? ()
> #14 0x08311f18 in gtreve_ ()
> #15 0x0831851f in gutrev_ ()
> #16 0x0871f919 in jumpt0_ ()
> #17 0x0b0f8ec8 in Maxpoints ()
> #18 0x0b0f8ca8 in gcbank_ ()
> #19 0x087a3e14 in load.1574 ()
> #20 0x082801f1 in gtrig_ ()
> #21 0x082800a8 in grun_ ()
> #22 0x08205e20 in hdgeant_ () at hdgeant_f.F:29
> #23 0x0805385f in main () at hdgeant.cc:7
>
>
> #2 0x08061036 in guhadr_ () at guhadr.F:131
> 131 CALL GFMFIN
> Current language: auto; currently fortran
> (gdb) list
> 126 IF (IHADR.LT.3) THEN
> 127 CALL GHEISH
> 128 ELSE IF (IHADR.EQ.3) THEN
> 129 CALL FLUFIN
> 130 ELSE
> 131 CALL GFMFIN
> 132 ENDIF
> 133 END
>
>
> Mark M. Ito wrote:
>> Experts,
>>
>> Using version from release-2008-10-21, control.in attached.
>> BMS_OSNAME = Linux_Fedora9-i686-gcc4.3.0
>>
>> **** GTCKOV: error from GLISUR = 1
>> GGPERP - geometry check error for shape #12!
>> **** GTCKOV: error from GLISUR = 1
>> GGPERP - geometry check error for shape #12!
>> **** GTCKOV: error from GLISUR = 1
>> GGPERP - geometry check error for shape #12!
>> **** GTCKOV: error from GLISUR = 1
>> GGPERP - geometry check error for shape #12!
>> **** GTCKOV: error from GLISUR = 1
>> GGPERP - geometry check error for shape #12!
>> **** GTCKOV: error from GLISUR = 1
>> **** GTRIGI: IEVENT= 4000 IDEVT= 4000 Random Seeds = 1574106590
>> 226018363
>> 4000 events simulated
>> Segmentation fault
>>
>> The reported error may or may not have something to do with the seg
>> fault. It appeared many times well before the crash on several events.
>>
>> -- Mark
>>
>
--
------------------------------------------------------------------------
David Lawrence Ph.D.
Staff Scientist Office: (757)269-5567 [[[ [ [ [
Jefferson Lab Pager: (757)584-5567 [ [ [ [ [ [
http://www.jlab.org/~davidl davidl@jlab.org [[[ [[ [[ [[[
------------------------------------------------------------------------