From: Robert Hancock <hancockrwd@gmail.com>
To: Sudarshan Soma <sudarshan12s@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch related to SIGSEGV handling in multiple threads and hung threads
Date: Fri, 15 May 2009 19:15:35 -0600 [thread overview]
Message-ID: <4A0E13B7.90200@gmail.com> (raw)
In-Reply-To: <de72ca4e0905150405w495a359ei7c4a625ff82edb11@mail.gmail.com>
Sudarshan Soma wrote:
> Hi ,
> I have a program which will create multiple threads. One of the thread
> receives SIGSEGV and it prints stacktrace in its handler and calls
> _exit(-1). The call to exit wont terminate all threads in a process
> and hence thread hangs here. This causes resouce leaks and other
> problems. It is seen only on linux 2.4.20.
>
> For printing stacktrace it uses
> __builtin_return_address and __builtin_frame_address
>
>
> The same program works fine on linux 2.6.26 kernel. It will exit the
> whole process when one of its thread dies as above.
>
>
> Please let me know the patch details or any workaround, if any. This
> is a bit urgent, so please let me know for any pointers , if any
>
> Thanks and Best Regards,
> Pavan.
That doesn't seem surprising, the old LinuxThreads thread implementation
normally used with the 2.4 kernels was pretty poor. However it would
likely be better to re-raise the signal rather than trying to exit out
of the signal handler.
prev parent reply other threads:[~2009-05-16 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 11:05 patch related to SIGSEGV handling in multiple threads and hung threads Sudarshan Soma
2009-05-16 1:15 ` Robert Hancock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0E13B7.90200@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudarshan12s@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox