[Top][All Lists]

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

Re: [Libunwind-devel] Re: [patch 2/2] Allow caller to block signals.

From: Mark Rabkin
Subject: Re: [Libunwind-devel] Re: [patch 2/2] Allow caller to block signals.
Date: Fri, 25 Sep 2009 11:29:31 -0700
User-agent: Microsoft-Entourage/

Hey Guys,

Sorry to jump in late here but could you give a couple more sentences of
clarification of what this patch intends to accomplish?

Is this simply a performance gain by allowing the users of
google::GetStackTrace() to block signals once (and maybe lock a mutex) at a
higher level of libunwind?  Or does this help ensure correctness and more
complete stack traces?

I'm wondering if we should turn this option on in our multithreaded servers
that take a lot of traces (sampling some various activities).

- Mark

On 9/25/09 11:25 AM, "Paul Pluzhnikov" <address@hidden> wrote:

> On Fri, Sep 25, 2009 at 10:59 AM, Arun Sharma <address@hidden> wrote:
>> Does:
>> #include "config.h"
>> work?
> I didn't think I was allowed to do that in client code, but I guess I am.
> Attached patch makes the test-async-sig pass.
> Thanks,

reply via email to

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