7 Apr
2018
7 Apr
'18
1:58 p.m.
On April 7, 2018 6:18:39 AM GMT+02:00, "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
On 04/01/2018 07:43 PM, David C. Rankin wrote:
I was looking for confirmation of the bug and whether the devs want
it
filed here to track or to not waste time filing with Arch and just file upstream?
I suspect this is a gcc-libs/valgrind issue, I updated https://bugs.archlinux.org/task/49681 with the information.
Please bring this issue upstream, where it could actually be fixed. Cheers, Levente