Bug 114 – Segmentation fault in MRes.c when JName=0x0

Bug 114 - Segmentation fault in MRes.c when JName=0x0

Summary:

Segmentation fault in MRes.c when JName=0x0

Status:	RESOLVED INVALID

Product:	TORQUE
Component:	pbs_server
Version:	3.0.x
Platform:	PC Linux

Importance:	P5 critical
Assigned To:	David Beer

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-02-17 03:24 MST by alexander.oltu
Modified:	2011-03-09 01:25 MST (History)
CC List:	2 users (show)

See Also:

Attachments
add extra checks (580 bytes, patch) 2011-02-17 03:25 MST, alexander.oltu	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description alexander.oltu 2011-02-17 03:24:11 MST

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.

Comment 1 alexander.oltu 2011-02-17 03:25:45 MST

Created an attachment (id=72) [details]
add extra checks

Comment 2 alexander.oltu 2011-02-21 02:32:00 MST

Sorry, I opened this bug as a Torque bug, but this is a MAUI bug. Could someone
point me to MAUI bugzilla?

Thanks,

Comment 3 Chris Samuel 2011-03-09 01:25:05 MST

I don't believe there is one I'm afraid, your best bet may be the mauiusers
mailing list.