[Top][All Lists]

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

[Libunwind-devel] Re: Ltest-nomalloc failure

From: Arun Sharma
Subject: [Libunwind-devel] Re: Ltest-nomalloc failure
Date: Thu, 28 Oct 2010 11:42:13 -0700

On Wed, Oct 27, 2010 at 10:06 PM, Zach Welch <address@hidden> wrote:
> On 10/26/2010 09:50 AM, Arun Sharma wrote:
> > On Mon, Oct 25, 2010 at 9:08 PM, Zach Welch <address@hidden> wrote:
> >
> >> Setting a breakpoint on malloc when running Ltest-nomalloc shows that
> >> fopen() indirectly allocates memory. I am not sure how to prevent that,
> >> but here's a backtrace for our mutual amusement and consideration.
> >>
> >
> > x86 defaults to:  --enable-debug-frame=no, so it shouldn't be an issue.
> > There are other code paths that result in calls to malloc when this option
> > is enabled.
> Disabling that option did allow this test to pass. Thanks!
> Which platforms require --enable-debug-frame by default?

ARM is the only one using it AFAIK.

> I have a stack
> of patches pending that clean up the build system, and I could add one
> that sets the correct default for this option. Thus, users would only
> need to specify --{enable,disable}-debug-frame when they want to use a
> non-standard configuration. Does this sound like a desirable change?

Yes - this would be a good change to have.

> Also, it would seem vaguely logical to skip the nomalloc test when
> libunwind is configured with --enable-debug-frame=yes.

I think the failure should stay as a reminder to get these code paths
fixed one day.


reply via email to

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