* pthread_sighandler
@ 2002-03-19 4:56 Joy Mukherjee
2002-03-19 17:33 ` pthread_sighandler george anzinger
0 siblings, 1 reply; 2+ messages in thread
From: Joy Mukherjee @ 2002-03-19 4:56 UTC (permalink / raw)
To: linux-kernel
hi !
I apologize for this this probably inappropriate question but i am writing as
a last option - how can I know at which instruction (the IP) a thread was
interrupted by SIGALRM ? Thank you very much and sorry once again .
Joy.
Joy Mukherjee
Graduate Student,
Deptt. of Computer Science,
Virginia Tech.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: pthread_sighandler
2002-03-19 4:56 pthread_sighandler Joy Mukherjee
@ 2002-03-19 17:33 ` george anzinger
0 siblings, 0 replies; 2+ messages in thread
From: george anzinger @ 2002-03-19 17:33 UTC (permalink / raw)
To: Joy Mukherjee; +Cc: linux-kernel
Joy Mukherjee wrote:
>
> hi !
> I apologize for this this probably inappropriate question but i am writing as
> a last option - how can I know at which instruction (the IP) a thread was
> interrupted by SIGALRM ? Thank you very much and sorry once again .
>
I am not going to do all your research for you, but you just need to set
up a signal handler for SIGALARM with the capability of recovering the
process state. I think this is the third parameter in the handler
call. You will need to look at the signal man pages to find out how to
do this and, most likely you will need to find the header file that
describes the state structure to figure out what member has what you
want.
--
George george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-03-19 17:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-19 4:56 pthread_sighandler Joy Mukherjee
2002-03-19 17:33 ` pthread_sighandler george anzinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox