https://bugs.kde.org/show_bug.cgi?id=441474
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #2 from Mark Wielaard <m...@klomp.org> ---
(In reply to Andreas Arnez from comment #1)
> (In reply to Mark Wielaard from comment #0)
> > [...] I haven't
> > identified precisely why valgrind is failing (it is only on s390x during the
> > gdbserver_tests/nlvgdbsigqueue testcase), [...]
> Does this mean the test case is failing for you? It isn't for me. If you
> have more information, I'd look into that.
Unfortunately the issue occurs on an remote test machine that checks against
latest gcc and glibc, where before this workaround it blows up the machine,
because vgdb eats up all memory and afterwards the nlvgdbsigqueue does indeed
FAIL.
So I would at least like to get this workaround in to not break the testing
setup.
I am trying to get access to a s390x setup where this happens. It might be
similar to the other issue I have seen with latest glibc, where if we get a
fatal signal, try to terminate and call __libc_freeres we get a SIGSEGV.
--
You are receiving this mail because:
You are watching all bug changes.
