Hi,
I'm struggling a bit here; I wanted to try and bisect pcre2 upstream
commits to see where this bug might have been introduced (or get to the
bottom of what link-grammar's test is doing wrong, I see they've been
troublesome in the past cf #975696).
I took unstable's link-grammar source, and built it thus:
./autogen.sh
#the python test fails for some reason
./configure --disable-python-bindings --disable-java-bindings
make
make check
I then cloned pcre2 upstream, checked out pcre2-10.42
./autogen.sh
./configure --prefix=/home/matthew/junk/pcre2bug/install
make
make install
Then I go back to my link-grammar tree and do
cd tests
LD_LIBRARY_PATH=/home/matthew/junk/pcre2bug/install/lib make check
which works
similarly
LD_LIBRARY_PATH=/home/matthew/junk/pcre2bug/install/lib ./multi-thread
works
With a slightly horrible hack:
lsof -p $(ps waux | grep multi-thread | grep pcre | cut -f 4 -d ' ')
I can confirm the running multi-thread test is definitely running my
locally-built (and thus 10.42) pcre2 library.
...so I'm not currently able to reproduce this in any way that might
help me track down what if anything in pcre2 changed. And I'm not sure
upstream would be very happy with "this test suite from another package
now fails in Debian CI" as a bug report...
Regards,
Matthew
