Problems with driver 180.22 and Pro-Engineer

[paulgress]

Just installed the latest released driver on my laptop running OpenSolaris nv104. Prior to the driver upgrade I had no problems opening and starting Pro-Engineer WF4. Now it won't start at all and gives me a segmentation fault and a core dump.

Doing a truss -f I found this error (posting a few lines before and after):

xstat(2, "/Disk1/Binaries/Pro-Engineer/WF4/sun_solaris_x64/obj/MOZILLA/components/libpipnss.so", 0x081408D8) = 0
1693/1: xstat(2, "/Disk1/Binaries/Pro-Engineer/WF4/sun_solaris_x64/obj/MOZILLA/components/nsProgressDialog.js", 0x081408D8) = 0
1689/1: Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFD7FFCAD67AD
1689/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x1ED8297C
1689/1: Received signal #11, SIGSEGV [default]
1689/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x1ED8297C
1693/1: xstat(2, "/Disk1/Binaries/Pro-Engineer/WF4/sun_solaris_x64/obj/MOZILLA/components/necko_about.xpt", 0x081408D8) = 0
1693/1: xstat(2, "/Disk1/Binaries/Pro-Engineer/WF4/sun_solaris_x64/obj/MOZILLA/components/nsProxyAutoConfig.js", 0x08140A28) = 0
1689/3: lwp_create() (returning as new lwp ...) = 0

Any other clue how to debug this or should I just reinstall the prior 177 series driver. Other than Pro-Engineer, the driver appears to be faster and functioning properly.

[johnmartin]

This is fixed in driver 180.35.