Description of problem: starting pvmd3, results in a SIGSEGV Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.run pvmd3 Actual results: daemon segfaults Expected results: daemon runs and listens for incomming pvm connections Additional info: This problem may be indicative of a larger problem with the library or header file layout, as both segfaults which I observed and corrected were the result of 64 bit pointers of which only the lower 32 bits were filled out (the upper 32 bits were 0xffffffff). I've managed to fix both segfaults and get the daemon working again by strictly including the appropriate files which the man pages for the corresponding failing library calls indicate (stdarg.h in addition to stdio.h for the vfprintf call, and time.h rather than sys/time.h for the failing ctime call). Without these modification, both these library calls encounter pointer errors.
Created attachment 96043 [details] patch to correct type mis-definition in vfprintf and ctime to avlid SIGSEGV This patch repairs the two segfaults encountered in the description of this bug.
Unfortunately, I think this scratches the surface of a much deeper problem w/ pvm and x86-64. I get other segfaults (particularly in the exit path) even with the patch applied.
3.4.4-16 is in rawhide, including this patch.
RHEL3 U2 for AMD64 and EM64T product still contains pvm-3.4.4.13 which exhibits this bug. I am trying to get PVM to work on a Dell EM64T (ia32e) system. Here is the error message I am getting when I try to start PVM. [root@localhost root]#pvm libpvm [pid4648] mksocs() connect: No such file or directory libpvm [pid4648] socket address tried: /tmp/pvmtmp004654.0 libpvm [pid4648] mksocs() connect: No such file or directory libpvm [pid4648] socket address tried: /tmp/pvmtmp004654.0 libpvm [pid4648]: Console: Can't contact local daemon
BZ 123919 could be related to this issue.
It's the same issue.
Er, wow, I actually didn't apply the patch in 3.4.4-16. I guess I didn't drink enough coffee when I closed this the first time.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-325.html