LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Regular Expression causes LabVIEW crash

Your PCRE library is 32 bits, can't use it.  We've nuked 32 bits LabVIEW as of LabVIEW2012 (for better or for worse).

 

I didn't write that VI, but debugged the problem, and yes the final regexp is the problem.  I replaced it with a simpler custom VI, the "replacements" are not that complicated to make.

 

We've been using that VI for about 6 years and this is the first time we bumped into this.

 

I've been using Perl and regexes (on 64 bit linux) since sometime in late 90s, but, maybe accidentally, never created something that recurses so much and crashes the stack.

 

 

0 Kudos
Message 11 of 16
(371 Views)

@instrumento wrote:

Your PCRE library is 32 bits, can't use it. 

 


Hmm, it should work for 32 bit and 64 bit - both compiled DLLs are in the pcre subfolder and should be loaded. Ok, For now it's not fully tested on 64 bit but I had no issue to execute regex-crash-01.vi with 64 bit labview. If you still have a problem with it, then check whether the correct path is entered in the call library nodes.

0 Kudos
Message 12 of 16
(365 Views)

Opening regex-crash-01.vi directly, or from the project, it is looking for lvpcre_norecurse64.dll, which is not in your zip file.

0 Kudos
Message 13 of 16
(355 Views)

@instrumento wrote:

Opening regex-crash-01.vi directly, or from the project, it is looking for lvpcre_norecurse64.dll, which is not in your zip file.


Thank's for this information. Save for previous removed the 64 bit DLLs ...

 

 

0 Kudos
Message 14 of 16
(351 Views)

For those of you interested on whether/how NI will solve the crash this is now:

  LabVIEW Bug 3787934: Search and Replace String in Regular Expression mode crashes LabVIEW

0 Kudos
Message 15 of 16
(283 Views)

@instrumento wrote:

For those of you interested on whether/how NI will solve the crash this is now:

  LabVIEW Bug 3787934: Search and Replace String in Regular Expression mode crashes LabVIEW


good to know. This is seems to me like a general issue of the pcre library. The newer pcre2 library has more an better control over such things and works also with the standard parameters. Only the jit version runs out of stack (but does not crash). The little issue with pcre2 is rather that it doesn’t fit as well as pcre with what we currently have in LabVIEW.

0 Kudos
Message 16 of 16
(268 Views)