19 Oct
2009
19 Oct
'09
8:47 a.m.
Jan Janak writes:
Yes, I think this is a bug. The bug won't be
triggered if event_parser
is only called from parse_event, but given that some modules use
event_parser directly, it can happen that it will try to read a
character which does not belong to the string given in arguments
anymore.
i have seen it happening a couple of times, i.e., event didn't have
params, but the next char in memory just happened to be ';'.
-- juha