Thanks - the crash report can be unpacked via apport-unpack:
$ gunzip _usr_bin_whoopsie.108.crash.gz $ apport-unpack _usr_bin_whoopsie.108.crash lp1850608
Then the contents can be seen in the lp1850608 directory - looking at StackTrace in particular we see the following:
... #11 0x0000563d8f963194 in upload_report (message_data=0x7f1dc0b60010 "r\276\003", message_len=140728898666098, s=0x7ffe5de79f00) at src/whoopsie.c:328 curl = 0x563d9001f8e0 result_code = CURLE_OK response_code = 0 list = 0x563d90027190 __func__ = "upload_report" ...
And that message_len looks suspiciously large
Thanks - the crash report can be unpacked via apport-unpack:
$ gunzip _usr_bin_ whoopsie. 108.crash. gz whoopsie. 108.crash lp1850608
$ apport-unpack _usr_bin_
Then the contents can be seen in the lp1850608 directory - looking at StackTrace in particular we see the following:
... data=0x7f1dc0b6 0010 "r\276\003", message_ len=14072889866 6098, s=0x7ffe5de79f00) at src/whoopsie.c:328
response_ code = 0
#11 0x0000563d8f963194 in upload_report (message_
curl = 0x563d9001f8e0
result_code = CURLE_OK
list = 0x563d90027190
__func__ = "upload_report"
...
And that message_len looks suspiciously large