> the function crash_signature_addresses is used to create the StacktraceAddressSignature.
Yes, but that's not a bug, but by design. This is being used for client-side (whoopsie) duplicate detection, and we can't rely on a "real" crash signature on the client side. The retracer on the other hand should stop looking at SAS once it figured out a crash_signature(). We should not muddy the semantics of SAS by sometimes putting in different information.
Can you please explain what the real issue is here? I figure we need to change something in apport-retrace or crashdb.py, but I don't think this should change the behaviour of user boxes that report crashes.
What is the exact issue here?
> the function crash_signature _addresses is used to create the StacktraceAddre ssSignature.
Yes, but that's not a bug, but by design. This is being used for client-side (whoopsie) duplicate detection, and we can't rely on a "real" crash signature on the client side. The retracer on the other hand should stop looking at SAS once it figured out a crash_signature(). We should not muddy the semantics of SAS by sometimes putting in different information.
Can you please explain what the real issue is here? I figure we need to change something in apport-retrace or crashdb.py, but I don't think this should change the behaviour of user boxes that report crashes.
Thanks!