[sr-dev] possible bug in parser/parse_event.c

looks like sr parser/parse_event.c has the same bug that i found in opensips although the implementations are different. after statement end = skip_token(tmp.s, tmp.len); end points to next char after event string. then end is assigned to tmp.s tmp.s = end; and after that if statement compares this next char to ';': if (tmp.s[0] == ';') { which looks wrong to me, because that char can be anything if event does not have any params. perhaps someone else can recheck if i'm right or wrong. -- juha