Reproduction Part 2
===================
I used divide-by-zero from chaos-marmosets to create a crash file and
deleted parts of CoreDump. Then I used following snippet to test the
modified crash file:
```python
import sys, apport
report = sys.argv[1]
r = apport.Report()
with open(report, 'rb') as f:
r.load(f, binary='compressed')
r.add_gdb_info()
```
I only got these three types of call traces:
```
EOFError: Compressed file ended before the end-of-stream marker was reached
binascii.Error: Incorrect padding
binascii.Error: Invalid base64-encoded string: number of data characters
(21189) cannot be 1 more than a multiple of 4
```
Chaning one character in CoreDump triggered a different error message:
```
gzip.BadGzipFile: CRC check failed 0xfb18ba58 != 0x7f1b4388
```
So it is unclear to me how to produce a faulty CoreDump entry in the
crash report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947800
Title:
/usr/share/apport/whoopsie-upload-
all:zlib.error:/usr/share/apport/whoopsie-upload-
all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1947800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
