[pcre-dev] [Bug 1749] PCRE-JITted code should be executed from non-writable memory to obey execmem SELinux restriction

https://bugs.exim.org/show_bug.cgi?id=1749 --- Comment #21 from Petr Pisar --- The error code is visible in the strace output I quoted in the comment #16. Return value is -1 and errno is EACCES. This failure is result of the SELinux policy that not only prevents from having

Re: [pcre-dev] PCRE2 on Coverity Scan

On Sun, 18 Dec 2016, Giuseppe D'Angelo wrote: > It was indeed the 10.22 tarball, which ships as part of Qt. OK, so it won't have all the latest patches. I'm planning on putting out 10.23-RC1 in January with a view to an actual release at the end of the month. > I can only get a summary and

Re: [pcre-dev] PCRE2 on Coverity Scan

Hello, On Sun, Dec 18, 2016 at 1:14 PM, wrote: > On Sun, 18 Dec 2016, Giuseppe D'Angelo wrote: > >> It occured to me that PCRE2 is not on Coverity Scan. As I uploaded a >> build of PCRE2 as part of Qt, Coverity raised a bunch of issues in its >> code. I can't judge if

Re: [pcre-dev] PCRE2 on Coverity Scan

On Sun, 18 Dec 2016, Giuseppe D'Angelo wrote: > It occured to me that PCRE2 is not on Coverity Scan. As I uploaded a > build of PCRE2 as part of Qt, Coverity raised a bunch of issues in its > code. I can't judge if they're false positives. Did you upload the current head or the previous release?

[pcre-dev] PCRE2 on Coverity Scan

It occured to me that PCRE2 is not on Coverity Scan. As I uploaded a build of PCRE2 as part of Qt, Coverity raised a bunch of issues in its code. I can't judge if they're false positives. Do you think * it's worth to have a pcre2 project on Coverity? * it's worth to set up regular scans of it?