Hi,
I am trying to fix an erratic s/w problem , that is very hard to reproduce !
!!
Basically processes seem to freeze and do nothing.
When I perform a TRUSS , I get the following :
sigsuspend(0xEFFFED60) (Sleeping).
The strange thing is when I grep for sigsuspend in the code, I find that it
is not being called. Can this system call be called indirectly through anoth
er
system function . E.G I am calling pause but when I wrote an example functio
n
and performed a truss it showed pause() (Sleeping)!!
Also,
Is there any way, I can determine what signals the mask is allowing / blocki
ng!!!
The OS is SunOS.
Ta
Pat

[ Post a follow-up to this message ]

In article <bc0e3bd8.0402180801.e166a52@posting.google.com>,
pat.saunders@sis.securicor.co.uk (pat saunders) wrote:

> Hi,
> I am trying to fix an erratic s/w problem , that is very hard to reproduce
> !!!
> Basically processes seem to freeze and do nothing.
> When I perform a TRUSS , I get the following :
> sigsuspend(0xEFFFED60) (Sleeping).
> The strange thing is when I grep for sigsuspend in the code, I find that i
t
> is not being called. Can this system call be called indirectly through
> another

It could be called internally by library functions.

> system function . E.G I am calling pause but when I wrote an example funct
ion
> and performed a truss it showed pause() (Sleeping)!!
> Also,
> Is there any way, I can determine what signals the mask is allowing /
> blocking!!!
> The OS is SunOS.

I believe Solaris's truss has an option to show function calls in
addition to system calls.  If you use that option, you should be able to
determine what library is calling sigsyspend().

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

Barry Margolin <barmar@alum.mit.edu> writes:

> In article <bc0e3bd8.0402180801.e166a52@posting.google.com>,
>  pat.saunders@sis.securicor.co.uk (pat saunders) wrote:
> 
>
> It could be called internally by library functions.
> 
>
> I believe Solaris's truss has an option to show function calls in
> addition to system calls.  If you use that option, you should be able to
> determine what library is calling sigsyspend().

You can also use Solaris's pstack to dump the stack traces
for the process's threads. There are a number of useful tools
in /usr/proc/bin that are worth becoming familiar with.

-SEan

[ Post a follow-up to this message ]