From: Yubin Ruan <ablacktshirt@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-help@sourceware.org, "Carlos O'Donell" <carlos@redhat.com>,
Will Hawkins <whh8b@virginia.edu>,
spc@conman.org, noloader@gmail.com,
Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: Re: determine whether code is running in a signal handler context
Date: Mon, 27 Nov 2017 12:50:00 -0000 [thread overview]
Message-ID: <CAJYFCiMevbGKdJAkMoen8xq=gBZfbMmc5m-WsVtw=WsS97ORyA@mail.gmail.com> (raw)
In-Reply-To: <2606c307-a853-1fff-07a1-7f775f61d2b5@redhat.com>
2017-11-27 19:55 GMT+08:00 Florian Weimer <fweimer@redhat.com>:
> On 11/27/2017 09:42 AM, Yubin Ruan wrote:
>>
>> Still remember this thread? It turn out that determining whether or not
>> you
>> are currently in a signal handler is trivial with libunwind:
>
>
> This is incorrect. libunwind (or any other unwinder) relies on information
> which is not always available.
what information?
> And since you need to unwind the stack
> completely (if not executing in a signal handler), it is very slow.
slow speed is acceptable though.
Yubin
next prev parent reply other threads:[~2017-11-27 12:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 14:18 Yubin Ruan
2017-10-18 18:34 ` Carlos O'Donell
2017-10-19 1:52 ` Yubin Ruan
2017-10-19 2:19 ` Carlos O'Donell
2017-10-19 2:39 ` Will Hawkins
2017-10-19 3:12 ` Carlos O'Donell
2017-10-19 4:07 ` Yubin Ruan
2017-10-19 4:56 ` Carlos O'Donell
2017-10-19 4:19 ` Will Hawkins
2017-10-19 4:01 ` Yubin Ruan
2017-10-19 2:59 ` Sean Conner
2017-10-19 3:12 ` Sean Conner
2017-10-19 3:51 ` Yubin Ruan
2017-10-19 7:10 ` Jeffrey Walton
2017-10-20 10:32 ` Szabolcs Nagy
2017-10-20 11:23 ` Yubin Ruan
2017-10-20 11:31 ` Szabolcs Nagy
2017-10-20 17:19 ` Carlos O'Donell
2017-10-20 17:48 ` Szabolcs Nagy
2017-10-22 6:09 ` Carlos O'Donell
2017-10-22 23:39 ` where is the definition of idtype_t supposed to live? John Lumby
2017-10-23 13:57 ` Florian Weimer
[not found] ` <BN6PR22MB16662DE3DFB590B3D6006F81A3460@BN6PR22MB1666.namprd22.prod.outlook.com>
2017-10-23 14:20 ` Florian Weimer
2017-10-23 10:01 ` determine whether code is running in a signal handler context Szabolcs Nagy
2017-10-23 14:30 ` Carlos O'Donell
2017-10-24 1:00 ` Yubin Ruan
2017-11-27 8:43 ` Yubin Ruan
2017-11-27 11:55 ` Florian Weimer
2017-11-27 12:50 ` Yubin Ruan [this message]
2017-11-27 12:51 ` Florian Weimer
2017-11-27 12:58 ` Adhemerval Zanella
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='CAJYFCiMevbGKdJAkMoen8xq=gBZfbMmc5m-WsVtw=WsS97ORyA@mail.gmail.com' \
--to=ablacktshirt@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=noloader@gmail.com \
--cc=spc@conman.org \
--cc=szabolcs.nagy@arm.com \
--cc=whh8b@virginia.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).