topic Re: pthread_kill(threadid, sigusr2) dumps core with SIGSEGV in Operating System - Linux

pthread_kill(threadid, sigusr2) dumps core with SIGSEGV

KRUPASINDHU PRADHAN — Sat, 30 Aug 2008 05:31:26 GMT

Hello ,
I have
{MM8}root@Node2:/data/tmp# uname -a
Linux Node2 2.6.10-telco-1.46-mckinley-smp #1 SMP Fri May 30 18:29:43 UTC 2008 ia64 GNU/Linux
# ls /lib/libpthread*
libpthread-0.10.so libpthread.so.0

I have 2-processes (lets say p1 and p2)
p1 has about 49 threads
p2 has about 17 threads

If p1 hangs , then p2 sends a signal SIGUSR2 using pthread_kill(threadid_p1, sigusr2)

While doing so , pthread_kill dumped core, stack trace is as below
==========================
Program terminated with signal 11, Segmentation fault.
#0 0x20000000000ffef0 in pthread_kill () from /lib/tls/libpthread.so.0
(gdb) bt
#0 0x20000000000ffef0 in pthread_kill () from /lib/tls/libpthread.so.0
==============================

ls -lrt /lib/tls/libpthread.so.0
lrwxrwxrwx 1 root root 18 Aug 29 11:18 /lib/tls/libpthread.so.0 -> libpthread-0.60.so

Advance thanks for the help

Re: pthread_kill(threadid, sigusr2) dumps core with SIGSEGV

Dennis Handly — Sun, 02 Nov 2008 10:52:27 GMT

I seriously doubt you can do that. thread_t is private to the process. On HP-UX pthread_kill(3) says:
The signal is asynchronously directed to thread in the calling process.

Re: pthread_kill(threadid, sigusr2) dumps core with SIGSEGV

KRUPASINDHU PRADHAN — Sun, 02 Nov 2008 16:51:24 GMT

You are right..
In fact , its one process and has multiple threads. I got the root cause for this issue.
When you pass on invalid thread ID to pthread_kill, it dumps core.

int main (int argc, char* const argv [])
{
int iRet = 0;
iRet = pthread_kill (123, 0); /* 123 is invalid thread ID */
printf("iRet = %d\n", iRet);
return 0;
}

{MM4}root@Node2:/tmp# cc invalidthread.c -lpthread
{MM4}root@Node2:/tmp# ./a.out
Segmentation fault (core dumped)

I confirmed it. But I am baffled why would we get core dump instead of ESRCH error code.
As par man page of pthread_kill

!ESRCH!
the thread |thread| does not exist (e.g. it has already
terminated)

Re: pthread_kill(threadid, sigusr2) dumps core with SIGSEGV

Dennis Handly — Sun, 02 Nov 2008 21:08:53 GMT

>But I am baffled why would we get core dump instead of ESRCH error code.

Because exhaustively checking is costly and probably not required. And you don't have anything remotely like a valid pthread_t as you show in your other thread:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1284229