On Thu, 26 Feb 2015, Giuseppe D'Angelo wrote:
On 26 February 2015 at 12:39, Zoltán Herczeg hzmes...@freemail.hu wrote:
The message bus error is also interesting, not the usual segmentation
fault. I don't know this error, but according to wikipedia, a bus error is
a fault raised by
On Tue, 24 Feb 2015, Petr Pisar wrote:
On Tue, Feb 24, 2015 at 03:46:56PM +0100, Petr Pisar wrote:
regcomp
regerror
regexec
regfree
[...]
The good news is that the only common symbols (listed above) come from the
POSIX-ish compatibility libraries (libpcreposix.so.0, respectively
I have replaced the -RC1 tarballs with -RC2:
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Testing/pcre2-10.10-RC2.tar.gz
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Testing/pcre2-10.10-RC2.tar.bz2
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Testing/pcre2-10.10-RC2.zip
I don't think these are related. The problem is in test2, not in test19 (the
serialization test). Sparc64 JIT has not implemented yet. ARM 64 supports
unaligned access, so a possible alignment issue is unusual. Perhaps the program
counter is executing something from a wrong address.
Petr,
--- You are receiving this mail because: ---
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1591
Summary: PCRE Library Heap Overflow Vulnerability
Product: PCRE
Version: 8.36
Platform: All
OS/Version: All
Hi Petr,
thank you for running PCRE2 on many environments.
The AArch64 is worse. It compiles with JIT but crashes on tests:
FAIL: RunTest
=
PCRE2 C library tests using test data from ./testdata
PCRE2 version 10.10-RC1 2015-02-20
Testing 8-bit library
Test 0: Unchecked
On 26 February 2015 at 12:39, Zoltán Herczeg hzmes...@freemail.hu wrote:
The message bus error is also interesting, not the usual segmentation
fault. I don't know this error, but according to wikipedia, a bus error is a
fault raised by hardware when a process is trying to access memory that
