Debugger hangs on UnixWare 7.1.1

[clement tang]

Hi,

I have a problem to run debugger (debug) on UnixWare 7.1.1. We were
able to run it a few times then the debugger hangs. It simply won't
take any command and I have to use kill -9 to kill the process (tried
kill but does not work).

Any suggestion to debug the debugger and to resolve it? It is
important to us because we were only able to debug with printf (or
cout) statement and it takes 10x more time than usual.

Thanks!

clement

%ulimit -a
time(seconds) unlimited
file(blocks) 2097152
data(kbytes) 393216
stack(kbytes) 32768
memory(kbytes) unlimited
coredump(blocks) 32768
nofiles(descriptors) 64
vmemory(kbytes) 409600

Here is some parameter to configure the machine. We also reserve
SHLBMAX 6
SDATLIM 0x18000000
HDATLIM 0x18000000
SSTKLIM 0x2000000
HSTKLIM 0x2000000
SVMMLIM 0x19000000
HVMMLIM 0x19000000

[J. L. Schilling]

Post by clement tang
I have a problem to run debugger (debug) on UnixWare 7.1.1. We were
able to run it a few times then the debugger hangs. It simply won't
take any command and I have to use kill -9 to kill the process (tried
kill but does not work).
Any suggestion to debug the debugger and to resolve it? It is
important to us because we were only able to debug with printf (or
cout) statement and it takes 10x more time than usual.

Would need more details on the nature of the application and the
debugging session. Does app use threads or fork subprocesses?
Is app being started from within debugger or grabbed from outside?
What debugger commands were used up to the point of failure?
And so forth.

Jonathan Schilling

[clement tang]

We were able to run the debugger but I think (after went over my
activities log) it starts to hang after we rebuild the kernel to
allocate more resource for regular user.

cputime unlimited
filesize 1048575 kbytes
datasize 393216 kbytes
stacksize 32768 kbytes
coredumpsize 16384 kbytes
descriptors 64
memoryuse 409600 kbytes

Kernel configuration parameters:
SHLBMAX 6
SDATLIM 0x18000000
HDATLIM 0x18000000
SSTKLIM 0x2000000
HSTKLIM 0x2000000
SVMMLIM 0x19000000
HVMMLIM 0x19000000

The debugger just hang with no response once we start it. It hangs
before I can bind to any application. I means I simply type debug at
command prompt and nothing I can do. What can you suggest me to try?

clement

[J. L. Schilling]

Post by clement tang
The debugger just hang with no response once we start it. It hangs
before I can bind to any application. I means I simply type debug at
command prompt and nothing I can do. What can you suggest me to try?

What happens if you run it in command line mode, using the debug -ic option?
You should get a "debug>" prompt.

If that works, it means graphics (Motif or X) is messed up. Try running
another X app such as xterm or xclock and make sure those work.

If that doesn't work, run "truss debug -ic" and see how far it gets in
the system call trace.

Jonathan Schilling