Bug #195
error in idmef_criteria_new_from_string
0%
Description
I am calling "idmef_criteria_new_from_string" for
a few strings. Here are my expressions:
alert.classification.text = "whatever" alert. = alert.classification.text = "whatever" alert.classification.text = "whatever"
Note, that the first, third and 4th expressions
are valid (and all the same), the second one is
invalid.
Calling idmef_criteria_new_from_string with the
first string returns 0, ok.
The second expression returns an error, saying
"syntax error". Ok.
But now on the third one I still get an error:
"syntax error". It seems there is some state
left in the lex parsing of the string???
This does not happen if I modify the second
string to
"alert. = bla"
which is still invalid (gives
the third string is parsed ok...
History
#1 Updated by Yoann VANDOORSELAERE almost 17 years ago
- Status changed from New to Assigned
#2 Updated by Yoann VANDOORSELAERE almost 17 years ago
- Status changed from Assigned to New
#3 Updated by Sebastien Tricaud almost 17 years ago
This is related to :
http://www.gnu.org/software/bison/manual/html_mono/bison.html#How-Can-I-Reset-the-Parser
I am working on this, thanks for reporting the issue.
#4 Updated by Yoann VANDOORSELAERE almost 17 years ago
- Status changed from New to Closed
- Resolution set to fixed
(In r8808) This work has been done by Sebastien Tricaud <toady@gscore.org> and myself:
- Reset Yacc status before parsing, fix #195.
- Enable YYERROR_VERBOSE for detailed error messages.
- Fix string memory leak on criteria syntax error.
- Fix possible criteria leak on criteria syntax error.
#5 Updated by Yoann VANDOORSELAERE over 14 years ago
- Project changed from PRELUDE SIEM to Libprelude
- Category deleted (
1) - Target version deleted (
0.9.13)