From: Alex Coplan <alex.coplan@arm.com>
To: Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: libbacktrace: Add support for MiniDebugInfo
Date: Wed, 16 Sep 2020 16:54:03 +0100 [thread overview]
Message-ID: <20200916155402.w2krbi4brg2qp6h4@arm.com> (raw)
In-Reply-To: <CAOyqgcW4fPho4cyDu3F21LAREuAESfOTVDtF884r8+heZ2c3ow@mail.gmail.com>
On 16/09/2020 07:26, Ian Lance Taylor wrote:
> On Wed, Sep 16, 2020, 4:03 AM Alex Coplan <alex.coplan@arm.com> wrote:
>
> > Hi Ian,
> >
> > On 14/09/2020 14:12, Ian Lance Taylor via Gcc-patches wrote:
> > > This patch to libbacktrace adds support for MiniDebugInfo, as
> > > requested in PR 93608.
> >
> > This appears to introduce a failure in the libbacktrace testsuite
> > (observed on both x86 and aarch64):
> >
> > ../gcc/libbacktrace/../test-driver: line 107: 7905 Segmentation fault
> > (core dumped) "$@" > $log_file 2>&1
> > FAIL: mtest_minidebug
>
>
>
> I tested on x86 without seeing anything like this. Can you give me any
> more details? Thanks.
Sure. On an Ubuntu 18.04 / x86-64 system with current trunk, configuring
with:
~/toolchain/src/gcc/configure \
--prefix=`pwd` \
--enable-languages=c,c++ \
--disable-multilib \
--disable-bootstrap
running `make && make check-libbacktrace` gives the failure described
above. Here is the contents of libbacktrace/test-suite.log:
=====================================================
package-unused version-unused: ./test-suite.log
=====================================================
# TOTAL: 33
# PASS: 32
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: mtest_minidebug
=====================
no debug info in ELF executable
no debug info in ELF executable
no debug info in ELF executable
no debug info in ELF executable
no debug info in ELF executable
no debug info in ELF executable
no debug info in ELF executable
test1: not enough frames; got 0, expected at least 3
test1: [0]: got expected f3
test1: [1]: got expected f2
FAIL mtest_minidebug (exit status: 139)
---
Let me know if you need any more info.
Thanks,
Alex
next prev parent reply other threads:[~2020-09-16 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 21:12 Ian Lance Taylor
2020-09-16 11:03 ` Alex Coplan
2020-09-16 14:26 ` Ian Lance Taylor
2020-09-16 15:54 ` Alex Coplan [this message]
2020-09-17 0:04 ` Ian Lance Taylor
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=20200916155402.w2krbi4brg2qp6h4@arm.com \
--to=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).