From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glibc: Enable backtrace from abort on ARM
Date: Fri, 9 Dec 2016 11:26:10 -0600 [thread overview]
Message-ID: <a429c8fc-8e0c-971b-9295-4056c09a614a@windriver.com> (raw)
In-Reply-To: <CAMKF1sphGgZP8-3DoPi+1Wv3DV6yDOAQW0Z5dNX=QFy16deLXA@mail.gmail.com>
On 12/9/16 12:48 AM, Khem Raj wrote:
> On Thu, Dec 8, 2016 at 11:03 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> +do_configure_append_arm () {
>> + echo "CFLAGS-abort.c = -funwind-tables" >> ${B}/configparms
>> + echo "CFLAGS-raise.c = -funwind-tables" >> ${B}/configparms
>> +}
>
> perhaps using -fasynchronous-unwind-tables is better. can you try that out ?
>
This passed my internal test with the same results.
So either one is fine with me. What is the difference between the options?
--Mark
next prev parent reply other threads:[~2016-12-09 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 19:03 [PATCH] glibc: Enable backtrace from abort on ARM Mark Hatle
2016-12-08 19:12 ` [morty] " Mark Hatle
2016-12-09 6:48 ` Khem Raj
2016-12-09 17:26 ` Mark Hatle [this message]
2016-12-09 17:36 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a429c8fc-8e0c-971b-9295-4056c09a614a@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox