[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173

["mark at klomp dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=23673

--- Comment #18 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Martin Liska from comment #17)
> (In reply to Mark Wielaard from comment #16)
> > (In reply to Martin Liska from comment #15)
> > > Thanks Mark, I installed the patch but I see still the same.
> > 
> > The output was exactly the same? That is surprising. So there is no
> > additional output that explains which failure path was taken? I would have
> > expected at least a message about the dwfl_getthreads call.
> 
> Yes:
> 
> $ ./backtrace-dwarf 
> 0x3ff8a9c0622	raise
> 0x3ff8a9a3ce2	abort
> ./backtrace-dwarf: dwfl_thread_getframes: no error
> 
> Looks that child correctly triggers assert.

Aha, ok, yes, I missed that dwfl_thread_getthreads just calls
dwfl_thread_getframes (there is only one thread) and this does indeed not find
the main frame. I'll tweak the testcase a bit more to make it show that.

But we now know for sure that it isn't the testframe infrastructure failing,
but that the unwinder really seems to not unwind through abort and so doesn't
find main. Still don't know what is happening though.

-- 
You are receiving this mail because:
You are on the CC list for the bug.