[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] cursor.is_interrupted() or is_...

From: Arun Sharma
Subject: Re: [Libunwind-devel] cursor.is_interrupted() or is_...
Date: Tue, 29 Jan 2008 11:39:46 -0800

On Jan 8, 2008 12:11 PM, Andrew Cagney <address@hidden> wrote:
Arun Sharma wrote:
> On Jan 8, 2008 7:42 AM, Andrew Cagney <address@hidden
> <mailto:address@hidden>> wrote:
>     what thoughts are there on adding a cursor method such as
>     is_interrupted() or is_caller() or ...?  The implementation would
>     likely
>     involve the addition of an extra bit field to the cursor.
> This sounds analogous to unw_is_signal_frame() - which is implemented
> without an extra bit.
>  -Arun
It is related yes; consider the back-trace:

  <signal>     is_interrupted=1 is_signal=1 -- inner
  handler()    is_interrupted=1 is_signal=0
  <signal>     is_interrupted=0 is_signal=1
  foo()        is_interrupted=1 is_signal=0
  main()       is_interrupted=0 is_signal=0 -- outer

Thanks for the explanation and sorry for the late response.
Yes, adding such a bit sounds useful.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]