I have a fairly long running script that has been running into an odd error. The error is "A syntax error occured parsing the Regular Expression : Access violation at address 7D611952 in module 'ntdll.dll'. Read of address 50435245."
I am using FinalBuilder 6.3.0.1885 on Win XP 64.
I am pretty certain that the regex: "^FullName:\s*(\S.*)\s*$" is correct, particularly since the statement runs several times before finally producing an error. Looking at the address 50435245, it looks a lot like part of an ASCII string, actually PCRE, a common regex library.
Which action is this, and what options do you have configured? We do use PCRE, in a number of places in FB so you will need to narrow it down for us to be able to attempt to reproduce the problem. Even better would be if you are able to extract enough from the project to reproduce the problem and that we can run here, that way we can run it under a debugger and see what is going on.
The "Text Find / Replace" Action "Search in variable contents" with the above Search String "Match as regular expression" and " Case Sensitive". Replacement used the $1 captured string to "Replace text and write back to variable" using "Substitute regulare expression matches". Behaviour was set to "Fail if there is LESS than 1 match". I'm not certain, but I vaguely recall seeing this particular expression fail after 3 successes.
Additionally, actions that used the perforce generic command, XML create nodes, and SQL iterator and execution were present.
I’ve been encountering the same type of error using regular expressions in output monitors, so this doesn’t seem to be limited to the Text / Find Replace Action.
The exceptions only occur after a large number of passes and seem to be deterministic in that for a given set of regular expressions spread through out the project and similar input, the project fails at the same point from starting the program and hitting “Run”. Additionally once the error occurs, faults will occur at any point that makes use of regular expressions.
Are you able to cobble together a project you can send us that reproduces the problem? I had a quick go here but after running in a loop for 20 minute it was still working fine, so I guess I don’t have a good test case.
Can see if there is a finalbuilderbugreport.text file in your %TEMP% folder, if so please email it to support. We now have another customer reporting the same error with the same action and output monitors. The error message is identical including the addresses. I’m hoping I can get a stack trace that will enable me to reproduce the error.
My attempts to reproduce this problem have gotten nowhere, I have a project that runs the Text Find /Replace action and another that has some regex output monitors inside a loop… so far it has run 10,000 iterations without a problem.
I have one project that on some input will error out fairly quickly, on other input the project runs until memory runs out due to processing multi-megabyte log files. So it would only happen when particular regular expression matches.
Some of the more interesting expressions that I'm using that match during crashes include:
Please try this build, it includes a bug fix from the regex vendor. I can’t say whether this fixes what you are seeing though as we have still not been able to reproduce the problem here.
No, 1949 was a bad build, not sure what the cause was (and no idea what that dialog is telling us) because I did another build without any check-in’s and it was fine. This is yesterday’s daily build :