Re: [getdata-devel] Make check failure: getdata-0.10.0

[D. V. W. <ge...@ke...>]

Hi Jeff,

Well, it certainly shouldn't be segfaulting, but I'm not sure if the bug
is in the test or the library, yet.

Disabing modules shouldn't make a difference.

What version of libpcre are you using?  Can you also send me your
config.log?

Cheers,
-don

>    Hello,
> 
>    I have successfully built getdata-0.10.0 with the new dynamic modules
>    behavior disabled (relevant library isn’t yet available on the shared
>    cluster I’m using).  The build proceeds fine, but make check has one
>    failure (copied below): a seg fault on match_pcre_js.
> 
>    Is this a known issue?  Any ideas?
> 
>    Thanks,
> 
>    Jeff
> 
>    PASS: match_pcre
> 
>    PASS: match_pcre_bad
> 
>    PASS: match_pcre_caseless
> 
>    PASS: match_pcre_ext
> 
>    libgetdata: Bad regular expression at offset 1: PCRE does not support
>    \L, \l, \N, \U, or \u
> 
>    n = 0 (expected 4)
> 
>    error = -24 (expected 0)
> 
>    entry_list = (nil) (expected non-NULL)
> 
>    /bin/sh: line 5: 19492 Segmentation fault      ${dir}$tst
> 
>    FAIL: match_pcre_js
> 
>    PASS: match_pcre_utf8
> 
>    PASS: match_regex
> 
>    PASS: match_regex_bad
> 
>    PASS: match_regex_ext
> 
>    PASS: match_regex_icase
> 
>    --------------------
>    Jeffrey Filippini
>    Assistant Professor of Physics and Astronomy
>    University of Illinois at Urbana-Champaign
>    405 Loomis Lab
>    1110 W Green St
>    Urbana, IL 61801
>    +1 (217) 244-4820
>    [1]jp...@il...
>    --------------------
> 
> References
> 
>    1. mailto:jp...@il...



> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: confirm 5084172385121a18c5e81b861b18dc038748b06b
> Sender: get...@li...
> From: get...@li...
> Date: Tue, 12 Sep 2017 19:03:35 +0000
> Message-ID: <mai...@li...>
> 
> If you reply to this message, keeping the Subject: header intact,
> Mailman will discard the held message.  Do this if the message is
> spam.  If you reply to this message and include an Approved: header
> with the list password in it, the message will be approved for posting
> to the list.  The Approved: header can also appear in the first line
> of the body of the reply.


-- 
D. V. Wiebe
ge...@ke...
http://getdata.sourceforge.net/