When looking up response codes, just keep the key on the stack.
authorGuy Harris <guy@alum.mit.edu>
Fri, 9 Mar 2018 02:02:21 +0000 (18:02 -0800)
committerGuy Harris <guy@alum.mit.edu>
Fri, 9 Mar 2018 02:03:15 +0000 (02:03 +0000)
commit7ffc4f96ebe2fac503cb251a848441ad8d4bad8c
tree35a3b7dbaa8553e0779e06e9233b17a4b7bdb46c
parent6e32335be61851592d8158772b743c55ae132eb9
When looking up response codes, just keep the key on the stack.

We don't need to dynamically allocate a guint variable to hold the
response code value - and then not bother to free it! - if we're just
doing a lookup; we can use an automatic variable and pass a pointer to
it.

Change-Id: I6edbb352f0aa33c91ede0f4e1bbb962fa921bea2
Reviewed-on: https://code.wireshark.org/review/26375
Reviewed-by: Guy Harris <guy@alum.mit.edu>
ui/cli/tap-sipstat.c