Juha Heinanen writes: > then i started to read parse_event.c/event_parser() code and it didn't > make sense to me: > > - after parsing the event, it goes to check if next char is ';': > > if( (*end)== ';') > > is that correct, because there may not be a next char, i.e., end may > point to random byte after the event string? if it does so, error > results if the next char happens to be ';'. > > - why is event sting copied to buf, for which i don't see any use in the > function?
i'm proposing the enclosed diff to parse_event.c in order to get rid of invalid error messages and unused buf. -- juha
parse_event.c-diff
Description: parse_event.c-diff
_______________________________________________ Devel mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
