CPAN module Proc::ProcessTable make test hangs

[Ralph Grothe]

Hi,

wonder if anyone has encountered this who can tell what is causing this, and hopefully has a remedy.

I have before succesfully installed Urist's module Proc::ProcessTable from CPAN on a 9000/800/N4000-44 under 11.00, and I'm cheerfully using it with no problems.

Now I tried to install it on a
9000/800/N4000-36
which has the same OS but (compared to the other box) a slightly dated patch level

# swlist -l bundle|grep -i patch
XSWHWCR1100 B.11.00.47 Hardware Enablement and Critical Patches
for HP-UX 11.00 (December 1999)


The make itself went smoothly but when I run make test it hangs here (and produces zombies):

# make test
/opt/build/Proc-ProcessTable-0.35/Process
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_har
ness(0, 'blib/lib', 'blib/arch')" t/*.t
t/process....# Failed test 1 in t/process.t at line 75
t/process....NOK 1

# ps -ef|grep defun|grep -v grep
root 1492 1259 2 Nov 14 ? 0:03
root 7001 6966 64 17:25:01 pts/0 0:00
# ps -fp 6966
UID PID PPID C STIME TTY TIME COMMAND
root 6966 6964 0 17:25:00 pts/0 0:00 /usr/bin/perl -MExtUtils::Comman
d::MM -e test_harness(0, 'bl



Because I'm using this module already with no problems on the N4000-44 (with a more recent patch bundle):

$ /usr/sbin/swlist -l bundle|grep -i patch
XSWGR1100 B.11.00.52.2 HP-UX General Release Patches, March 2001

XSWHWCR1100 B.11.00.52.3 HP-UX Hardware Enablement and Critical Pa
tches, March 2001

I suspect the cause to be a missing patch or something similar.

Does anyone know?

Regards
Ralph

[H.Merijn Brand (procura]

What perl?
PP-0.37 is out

[Ralph Grothe]

5.8.0

but please see attachment for dump of
perl -V

[H.Merijn Brand (procura]

Can't see anything strange with that. Looks darn perfect, even prepared for Oracle.

I must drop out here :/

[Derek A. Hackbardt]

Has anyone found a resolution to this issue?

I'm dealing with some systems that ran fine for ages on .35 Proc:ProcessTable, but now some are having issues after a handful of OS patches have been applied.

I've tried .38 too, with no luck and haven't had time to dig into the source to see if anything jumps out. Hopefully someone else already found a solution :)

Thanks,
Derek