[MDEV-14024] PCRE2 Created: 2017-10-06  Updated: 2023-04-17  Resolved: 2019-12-21

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: 10.5.1

Type: Task Priority: Critical
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
Relates
relates to MDEV-13412 main.func_regexp_pcre fails in buildb... Closed
relates to MDEV-16599 Add REGEXP_LIKE function Open
relates to MDEV-20377 Make WITH_MSAN more usable Closed
relates to MDEV-31061 ASAN: global-buffer-overflow in __int... Open
Sprint: 10.3.3-1

 Description   

PCRE1 is in maintenance mode, some bugs aren't getting fixed (see https://bugs.exim.org/show_bug.cgi?id=2173). The current PCRE branch is PCRE2, we need to migrate to it to continue getting our reported bugs fixed.



 Comments   
Comment by Alexey Botchkov [ 2018-04-02 ]

So that i removed the pcre/ subdirectory, added the pcre2/ subdirectory with the pcre2-10.31 sources, and then did these changes to the server code:
http://lists.askmonty.org/pipermail/commits/2018-April/012175.html

Comment by Sergei Golubchik [ 2018-04-11 ]

the first commit (remove pcre, add prce2) — did you do any changes to pcre2? or just unpacked the tarball?

Comment by Alexey Botchkov [ 2018-04-23 ]

I just unpacked the tarball.

Comment by Alexey Botchkov [ 2018-04-23 ]

http://lists.askmonty.org/pipermail/commits/2018-April/012444.html

Comment by Alexey Botchkov [ 2018-06-26 ]

patch v2
http://lists.askmonty.org/pipermail/commits/2018-June/012656.html

Comment by Sergei Golubchik [ 2018-11-23 ]

review sent

Comment by Marko Mäkelä [ 2019-08-26 ]

As noted in MDEV-20377, MemorySanitizer is finding several issues with the bundled PCRE1 (and according to serg the "libpcre3" on my Debian system actually is PCRE1). Also, I remember AddressSanitizer flagging issues when using -DWITH_PCRE=bundled. Using -DWITH_PCRE=system could merely hide those issues from ASAN.

I feel that this issue is all but blocking the use of MemorySanitizer.

Generated at Thu Feb 08 08:10:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.