On Thu, Apr 22, 2010 at 1:21 AM, Lassi Tuura <[email protected]> wrote: > I'll let those with more experience speak. For our purposes a signal frame > is just another frame and I am unfamiliar with libunwind uses which care > about the distinction. >
As I remember it, it was intended to provide a means to tell the user that normal flow of execution was interrupted. Analogous to the way gdb displays <signal handler> (or something like that) for a signal frame. At the kernel-level, "signal" should be read as "interrupt". --david -- eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768
_______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
