This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: determine whether code is running in a signal handler context

From: Florian Weimer <fweimer at redhat dot com>
To: Yubin Ruan <ablacktshirt at gmail dot com>, libc-help at sourceware dot org
Cc: Carlos O'Donell <carlos at redhat dot com>, Will Hawkins <whh8b at virginia dot edu>, spc at conman dot org, noloader at gmail dot com, Szabolcs Nagy <szabolcs dot nagy at arm dot com>
Date: Mon, 27 Nov 2017 12:55:21 +0100
Subject: Re: determine whether code is running in a signal handler context
Authentication-results: sourceware.org; auth=none
References: <CAJYFCiPkMNCr0X61AQ9MqhXyagOb0k4tTp5mRAD171VLkedVYQ@mail.gmail.com> <CAJYFCiOOhQz1XurSEFe08f7V4cyVFED24_5QmVtYqhu0TTWk4g@mail.gmail.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 oninformation which is not always available. And since you need to unwindthe stack completely (if not executing in a signal handler), it is veryslow.


Thanks,
Florian

Follow-Ups:
- Re: determine whether code is running in a signal handler context
  - From: Yubin Ruan

References:
- Re: determine whether code is running in a signal handler context
  - From: Yubin Ruan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]