>assign re $regcomp(test) >eval echo $regexec(re test) > >If you know how to use a debugger, it would be helpful if you >can get a stack trace, and cut and paste it here. > >Program received signal SIGSEGV, Segmentation fault. >0x420bcf9c in re_search_internal () from /lib/tls/libc.so.6 >(gdb) bt >#0 0x420bcf9c in re_search_internal () from /lib/tls/libc.so.6 >#1 0x420bc877 in regexec () from /lib/tls/libc.so.6 >#2 0x08067dc3 in function_regexec (input=0x80d952b "test") at functions.c:412 9
To follow up on this, the problem was that passing a string to $regex() that was not returned from $regcomp() causes epic to crash. It was suggested that epic could do some basic sanity checking, and I have effected that change. The return value from $regexec() should be of a known length (it is system dependant, but it can be calculated), and $regexec() will refuse any regex that is not exactly the right length. That should avoid the most likely errors. Thanks for the report! Jeremy _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
