[Wireshark code review <code-review-do-not-reply@xxxxxxxxxxxxx>]

URL: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=441cf84b51466919e755e9d30ea5cc9e78ecdfc7
Submitter: Balint Reczey (balint@xxxxxxxxxxxxxxx)
Changed: branch: lts-1.8.2
Repository: wireshark

Commits:

441cf84 by Evan Huus (eapache@xxxxxxxxx):

    rtsp: parse the correct token for the status code
    
    Don't call get_token_len on next_token *and* pass in next_token to store the
    subsequent pointer - the token we want to parse is the *current* value of
    next_token, not the next next token (which may be beyond the end of the buffer,
    if next_token happens to be the *last* token).
    
    Conflicts:
    	epan/dissectors/packet-rtsp.c
    
    Bug: 10381
    Change-Id: I9fb27e8bdaf2f9556f61841de30cec04b98ffb96
    Reviewed-on: https://code.wireshark.org/review/3663
    Reviewed-by: Evan Huus <eapache@xxxxxxxxx>
    (cherry picked from commit 73959159dbf34b4a0b50fbd19e05cb1b470be9b0)
    Reviewed-on: https://code.wireshark.org/review/3664
    (cherry picked from commit 949cca0810f7ed2f92adc16c57d2e4badb10a6a4)
    Reviewed-on: https://code.wireshark.org/review/3665
    Reviewed-on: https://code.wireshark.org/review/4424
    Reviewed-by: Balint Reczey <balint@xxxxxxxxxxxxxxx>
    Tested-by: Balint Reczey <balint@xxxxxxxxxxxxxxx>
    

Actions performed:

    from  49633a2   Fix an infinite loop when the line has no length
    adds  441cf84   rtsp: parse the correct token for the status code


Summary of changes:
 epan/dissectors/packet-rtsp.c |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)