q4 dies

[Herren Marc]

Hi,

I'm trying to analyse a core file on my HP11.11 workstation.

First everything went ok, but suddendly I get the following error while launching q4

...
q4: (warning) core file not opened
System memory: 0 MB
Couldn't load dumpdev_t, sorry.
Died at /usr/contrib/Q4/lib/q4lib/checkdump.pl line 47, chunk 14.

I'm really new to q4 so I searched the forum and the web for this error message but I couldn't find anything.

I've got enough free memory so I don't know to what the system memory message refers.

Any hints ?

Thanks

Marc

[Paula J Frazer-Campbell]

Hi

Check your process list and look for failed q4 attempts.

How big is the core file ?

Also can you post the output of:-

ps -ef

Paula

[Cheryl Griffin]

Marc,
This message means there is not a problem with q4, but the dump is corrupt:
"q4: (warning) core file not opened
System memory: 0 MB
Couldn't load dumpdev_t, sorry.
Died at /usr/contrib/Q4/lib/q4lib/checkdump.pl line 47, chunk 14. "

What was the panic string recorded to the crash INDEX and/or to the /etc/shutdownlog?

[Herren Marc]

Found the error myself

I used
-> q4 /tmp/vmunixq4
which worked for the first time but now crashes but

-> q4 /tmp/vmunixq4 /dev/mem

works fine ;)

Tnx.

Hope I can now find out the number of current threads per process.



Marc

[Michael Steele_2]

Is this a core file from an application or a crash dump from a system panic stored in '/var/adm/crash/core.0'? One will work but not the other. For the other use the 'strings' command.

strings core | more

[Steve Steel]

Hi


look at

http://www.informatik.uni-frankfurt.de/RBI/hp-service/patches/s700_800/11.X/PHCO_28067.txt

The patch may interest you


Steve Steel

I used to have a handle on life, but it broke

[James Murtagh · Accepted solution]

Hi Marc,

To find the current threads per process:

q4> load proc_t from proc_list next p_factp max nproc
q4> keep p_pid ==
q4> print -tx p_created_threads

To load the thread list from here:

q4> load struct kthread from p_firstthreadp next kt_nextp max (p_created_threads+1)

Regards,

James.

[Herren Marc]

James Murtagh:

Should it be p_livethreads which display the current number of threads ?

q4> print p_livethreads


Greets

Marc

[James Murtagh]

Hi Marc,

Yes, you are right. For some reason I was reading "current threads" but by brain was thinking "created threads". I did take this into account in the (p_created_threads+1) though which even confuses me! :-)

Also, I would advise against using the /dev/mem psuedo driver for q4 access, I think there was an issue with a race condition that could cause the server to panic in some cases. Don't know if this is resolved now but safer to use /dev/kmem instead.

Regards,

James

[Steven E. Protter]

This probably isn't the problem, but are you following a propery q4 procedure?

Attached:

SEP