On 20/11/17 22:22, Adrian Bunk wrote:
[snip]
One real-world problem where this dodgy code does break has been found
to affect real software, and the suggested patch that disables some
otherwise possible optimizations for one function is confirmed to
workaround this specific breakage.
This is a
Processing control commands:
> severity -1 serious
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Severity set to 'serious' from 'important'
> tags -1 -moreinfo
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Removed tag(s) moreinfo.
> found -1 2:8.
severity 878107 important
tags 878107 + upstream moreinfo
quit
Hi,
On 09/10/17 21:23, Ondřej Surý wrote:
> the system-wide pcre3 library stack frame size detection is broken as
> described in
> https://bugs.exim.org/show_bug.cgi?id=2173
I note that upstream aren't proposing to address this.
>
Processing commands for cont...@bugs.debian.org:
> severity 878107 important
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Severity set to 'important' from 'grave'
> tags 878107 + upstream moreinfo
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Ad
Package: src:pcre3
Version: 2:8.39-5
Severity: grave
Dear Maintainer,
the system-wide pcre3 library stack frame size detection is broken as described
in
https://bugs.exim.org/show_bug.cgi?id=2173
and that breaks at least ppc64el and s390x build causing segfaults in the test
suite (+ autopkgtes
5 matches
Mail list logo