6 Aug
2012
6 Aug
'12
9:32 a.m.
Am Sonntag, 5. August 2012, 14:54:55 schrieb Alex Balashov:
I wish I could tell what exotic SIP message caused
this, bug I am not
crafty enough with GDB, and a lot of values are optimised out because I
did not specifically compile with all debugging symbols in. But here's
what I've got:
[..]
More concretely:
(gdb) set print elements 0
(gdb) frame 22
#22 0x000000000049eb9e in receive_msg (
buf=0x8d84e0 "INVITE sip:19378983606 710@207.239.33.68:5060
SIP/2.0\r\nRecord-Route:
Hello Alex,
you could try to print the buf string explicitely. If you then copy this in a
text editor and remove the line breaks (/r/n) you should be able to recover
the SIP message.
Cheers,
Henning Westerholt