[torquedev] [Bug 114] New: Segmentation fault in MRes.c when JName=0x0

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Thu Feb 17 03:24:11 MST 2011


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=114

           Summary: Segmentation fault in MRes.c when JName=0x0
           Product: TORQUE
           Version: 3.0.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: pbs_server
        AssignedTo: dbeer at adaptivecomputing.com
        ReportedBy: alexander.oltu at bccs.uib.no
                CC: torquedev at supercluster.org
   Estimated Hours: 0.0


With our maui.cfg file we get:

Program terminated with signal 11, Segmentation fault.
#0  MResAdjustDRes (JName=0x0, ForceEval=0) at MRes.c:7447
7447        JRE[jreindex].Type = mreNONE;
(gdb) bt
#0  MResAdjustDRes (JName=0x0, ForceEval=0) at MRes.c:7447
#1  0x000000000042a45e in MSchedProcessJobs (OldDay=0x7fff6e7c9d50 "",
GlobalSQ=0x7fff6e7c3d40, GlobalHQ=0x7fff6e7bfd40) at MSched.c:6955
#2  0x000000000040596d in main (ArgC=1, ArgV=<value optimized out>) at
Server.c:192
(gdb) print JName
$1 = 0x0
(gdb) print JRE  
$2 = (mre_t *) 0x0

It is not reproducible with default cfg file.

The patch attached we are using to workaround this issue.

What this segfault is related to and is our solution OK?

PS. We can provide coredump and binary.

Thanks.

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list