From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gcc-patches@gcc.gnu.org, Ian Lance Taylor <iant@golang.org>,
Nathan Sidwell <nathan@acm.org>
Subject: Re: [backtrace] Avoid segfault
Date: Tue, 26 Feb 2019 21:08:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1902262137320.4073@anthias.pfeifer.com> (raw)
In-Reply-To: <ed27863c-b21e-f18f-818b-fbb6bf1f60b8@suse.de>
On Tue, 26 Feb 2019, Tom de Vries wrote:
>>> Specifically I am now seeing
>>>
>>> gmake[4]: *** No rule to make target 'b3test_dwz_buildid',
>>> needed by 'b3test_dwz_buildid.log'.
> The only way of reproducing it was to deinstall dwz.
:
> Fixed in patch below, committed as trivial.
Great, thanks for the quick follow-up, Tom! I did a couple of further
tests and am happy to report that the testsuite of libbacktrace is now
completely "clean".
I'll keep my eyes open. ;-)
Gerald
next prev parent reply other threads:[~2019-02-26 20:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 15:14 Gerald Pfeifer
2019-02-25 21:49 ` Tom de Vries
2019-02-26 8:37 ` Tom de Vries
2019-02-26 21:08 ` Gerald Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-25 0:15 Nathan Sidwell
2019-01-25 1:49 ` Ian Lance Taylor
2019-01-25 13:23 ` Tom de Vries
2019-01-25 14:10 ` Tom de Vries
2019-01-25 14:31 ` Ian Lance Taylor
2019-01-25 17:20 ` Nathan Sidwell
2019-01-25 17:31 ` Marek Polacek
2019-01-27 21:53 ` Tom de Vries
2019-01-28 1:39 ` Ian Lance Taylor
2019-01-29 8:52 ` Tom de Vries
2019-01-29 15:29 ` Ian Lance Taylor
2019-01-29 23:53 ` Segher Boessenkool
2019-01-30 2:21 ` Ian Lance Taylor
2019-01-25 14:23 ` 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=alpine.LSU.2.21.1902262137320.4073@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=nathan@acm.org \
--cc=tdevries@suse.de \
/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).