[Bug build/22916] debug/tst-backtrace4, debug/tst-backtrace5 fail on s390x when running on Linux 4.15 kernel

carlos at redhat dot com sourceware-bugzilla@sourceware.org
Fri Apr 27 14:12:00 GMT 2018


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

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Stefan Liebler from comment #4)
> I've just installed Ubuntu 18.04 with the kernel 4.15.0-20-generic.
> It seems as this kernel contains the mentioned commit
> as those tests are now passing on s390 (31bit).
> 
> How to proceed with this bugzilla? Can we just set it to resolved?

>From our perspective this was never a bug, and without a properly setup signal
frame there is no backtracing can work so there isn't even an easy way to
workaround this in userspace.

Marking RESOLVED/INVALID. Thanks for looking into this Stefan!

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


More information about the Glibc-bugs mailing list