topic Re: Process behaviour in Operating System - HP-UX

Process behaviour

Robert_73 — Mon, 15 Jul 2002 14:06:48 GMT

Hi List,
Is there any other commands available on UNIX other than TRUSS to find out the problem with a particular process or command?.
Thnaks in advance

Re: Process behaviour

Robert True — Mon, 15 Jul 2002 15:58:10 GMT

Shell scripts, of course, can have the 'set -x' placed in them.

Re: Process behaviour

RAC_1 — Mon, 15 Jul 2002 18:39:19 GMT

you can several freely available utilities in this regard. Also you can q4 to trace the process in the kernel.

If required I can post the detailed procedure for this.-q4

Regards,

Re: Process behaviour

Robert_73 — Mon, 15 Jul 2002 18:41:38 GMT

Anil,
I have no clue about the q4, could you please post the procedure? any utilities?.
Thanks

Re: Process behaviour

harry d brown jr — Mon, 15 Jul 2002 19:00:29 GMT

See this thread for info on q4:

http://forums.itrc.hp.com/cm/QuestionAnswer/0,,0xc6abd5fab40ed6118ff40090279cd0f9,00.html

live free or die
harry

Re: Process behaviour

RAC_1 — Mon, 15 Jul 2002 20:45:04 GMT

Check the thread.
Check the following.

Regards,

Use q4 to get a stack trace using the process ID number.

Note: q4 is available at HP-UX Version 10.10 and above. An example (using process id 21699):

# q4 /dev/mem /stand/vmunix

q4> load struct proc from proc max nproc; keep p_stat

loaded 1284 struct proc's as an array (stopped by max count)

kept 571 of 1284 struct proc's, discarded 713

q4> keep p_pid == 21699;trace pile

kept 1 of 571 struct proc's, discarded 570

stack trace for process at 0x843edc0 (pid 21699), thread at

0x8500300 (tid 28011)

process was not running on any processor

save+0x0

_swtch+0x138

real_sleep+0x330

_sleep_one+0x14

semop+0x71c

syscall+0x1a4

q4> quit
The above indicates that the process is sleeping after doing a semop call. The next step might be to see how this process is using semaphores or, if this is a system process, whether there are any known issues with this process sleeping on semop.

Steps to set up q4 on your system are as follows:

cd /usr/contrib/lib

uncompress Q4Lib.tar.Z:

tar -xvf Q4Lib.tar

cp /usr/contrib/lib/q4lib/sample.q4rc.pl ~/q4rc.pl
Change the following line in ~/q4rc.pl:

# push (INC, "/usr/local/lib/q4lib");
to

push (INC, "/usr/local/lib/q4lib");
Set up your PATH:

export PATH=$PATH:/usr/contrib/bin
Prep your kernel:

q4pxdb /stand/vmunix
Note: dde (requires DCE product) and analyze (10.01 and below) can also be used to look at a process's stack trace.

8. Public domain software such as trace can be used to trace a process's system calls. trace is available for download from the public domain software page located off of the www.software.hp.com Web site.

This software is particularly useful because it enables you to see what calls a process is making, if any, and whether the process is looping.

Re: Process behaviour

Steven Mertens — Mon, 15 Jul 2002 21:01:20 GMT

hi Robert,

You can also try tusc. You can find
it here :

http://hpux.cict.fr/hppd/hpux/Sysadmin/tusc-7.0/

Regards,

Steven

Re: Process behaviour

Steven Mertens — Mon, 15 Jul 2002 21:05:12 GMT

... or there's also the trace command :
http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/trace-1.6/

Steven

Re: Process behaviour

Mark Greene_1 — Tue, 16 Jul 2002 12:53:23 GMT

For commands, the first thing you want to do is capture the error code returned in $? and then check the man page for that command to interpret the code.

For binaries you can try trace or adb, the absolute debugger.

HTH
mark