From: Jose E. Marchesi <jose.marchesi@oracle.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Some Debian elfutils issues
Date: Mon, 18 Jan 2016 17:37:46 +0100 [thread overview]
Message-ID: <877fj62691.fsf@oracle.com> (raw)
In-Reply-To: 1453127747.7711.71.camel@klomp.org
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Thu, 2016-01-14 at 00:22 +0100, Kurt Roeckx wrote:
> On Wed, Jan 13, 2016 at 11:13:28PM +0100, Mark Wielaard wrote:
> > I looked at the latest build logs:
> > https://buildd.debian.org/status/package.php?p=elfutils
> > [...]
> > If you could try the attached patches on a new Debian build that would
> > be appreciated.
>
> I'll try it tomorrow or in the weekend.
Thanks for doing a build with the proposed patches. They seem to have
solved the issues on kfreebsd and the hurd port builds again (but still
fails one testcase). I have pushed the commits below to master.
The only thing that worries me is the sparc failure. I have CCed Jose
who might want to take a look. What is strange is that 0.165-1 and
0.165-2 PASS on sparc just fine. And I don't see anything in 0.165-3
that would explain the failure on sparc:
https://buildd.debian.org/status/logs.php?pkg=elfutils&arch=sparc64
The problem seems to be:
/«PKGBUILDDIR»/tests/backtrace: dwfl_thread_getframes: No DWARF information found
and that is probably triggered by this code in __libdwfl_frame_unwind:
Dwfl_Module *mod = INTUSE(dwfl_addrmodule) (state->thread->process->dwfl, pc);
if (mod == NULL)
__libdwfl_seterrno (DWFL_E_NO_DWARF);
I definitely can't reproduce this problem in my own sparc64-*-* setups.
next reply other threads:[~2016-01-18 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 16:37 Jose E. Marchesi [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-19 3:33 Kurt Roeckx
2016-01-18 14:35 Mark Wielaard
2016-01-13 23:40 Kurt Roeckx
2016-01-13 23:22 Kurt Roeckx
2016-01-13 22:13 Mark Wielaard
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=877fj62691.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=elfutils-devel@lists.fedorahosted.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).