Unable to Bring Up the Debugger WDB or GDB

[JULIE BROOKS]

Since upgrading our HP Workstations to an OS Level of 11.0, we have been unable to bring up the debugger. The message that we get is that virtual memory is exhaused and the requested memory cannot be allocated. We have tried everything including looking at every patch HP ever made. As another clue to our problem the following error message comes up when we attemt to bring up a graphics application: libGL Error: Application is not linked with shared pthread library. An X Windows Error Occurred X Error of failed request: Bad Access (attempt to access private resource denied) Major opcode of failed request: 141 Serial number of failed request: 10060. I have checked OpenGL and it seems to be installed correctly. Any help anyone can give will be appreciated. We have been working on this issue for almost a month!

[Santosh Nair_1]

Have you tried upgrading wdb to the latest 11.0 version, i.e. version 2.1 available from:

http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,1662,00.html

-Santosh

[JULIE BROOKS]

Yes, we are running the 2.1 version of the debugger. HP recommended going to 3.0 (?). I haven't tried that yet, because there are other parts of our company that are running the 2.1 version successfully. Thanks for the reply!

[Alex Glennie]

I'd be surprised if this is a graphics or OpenGl problem as if both wdb & gdb fail for the same reason / produce the same error (bear in mind gdb is not a gui.

as to your application : this could be a separate problem , best way to check if openGL is installed OK is to use /opt/graphics/OpenGl/demos/verify_install .

As to wdb 3.0 : never heard of it and no reference at http://www.hp.com/go/wdb either !

my advise would be to fireup glance and see what memory and other resources you maybe running out of ....

[Bill McNAMARA_1]

swverify WDB

look at /var/adm/swagent.log

swverify -F WDB
to repair installation problems (permissions etc..)

Later,
Bill