This is the mail archive of the libc-alpha@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: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.

From: Mark Wielaard <mark at klomp dot org>
To: Jim Wilson <jimw at sifive dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Tue, 22 Jan 2019 14:28:45 +0100
Subject: Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
References: <20190113234809.4818-1-jimw@sifive.com> <fe71f6cdfc7fe3970c38f06437fbc5cde8a78a57.camel@klomp.org> <CAFyWVaY=EcAMpW8Qn+-i9iqFtuaa0jrFGoFABwSYxKSJFnp0EQ@mail.gmail.com>

On Sun, 2019-01-20 at 21:55 -0800, Jim Wilson wrote:
> Or maybe my glibc is configured slightly differently than the
> system glibc and that is effecting the result.

The distro might build with -fasynchronous-unwind-tables which would
make sure that only the CFI unwinder is used, while without it, it
might be that there is a frame that might have to be handled by the
fallback unwinder.

> I do think the __thead_start change and the new testcase are correct.
> Other ports have similar changes to __thread_start, and verifying
> that unwind to top of stack in a thread works is a good test to do.

Agreed,

Mark

Follow-Ups:
- Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
  - From: Jim Wilson

References:
- [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
  - From: Jim Wilson
- Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
  - From: Mark Wielaard
- Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
  - From: Jim Wilson

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