From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: hook SIGSEGV
Date: Tue, 13 May 2014 17:29:38 +0200 [thread overview]
Message-ID: <20140513152938.GA4835@grml> (raw)
In-Reply-To: <EAF38085-83E5-461D-A31A-A20F5C0980FE@gmail.com>
Hi!
On 21:46 Sat 10 May , net.study.sea at gmail.com wrote:
>
> Hi all :
> I want to know is it possible to hook SIGSEGV to restart the thread which the signal is sent to,without restart the whole process? And record the place where has caused this signal?
>
> Thanks!
Yes, you can hook SIGSEGV like a normal signal. However, I have never tried to
do so...
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2014-05-13 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:46 hook SIGSEGV net.study.sea at gmail.com
2014-05-13 15:29 ` michi1 at michaelblizek.twilightparadox.com [this message]
2014-05-13 15:43 ` Sam Dodrill
2014-05-13 16:02 ` Yann Droneaud
2014-05-14 12:14 ` Kristof Provost
2014-05-14 22:15 ` Max Filippov
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=20140513152938.GA4835@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).