disambiguate crash dumps being in memory or files

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: lars, Assigned: lars)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

3 years ago
there has been a bifurcation in the crash storage data throughout the history of the classes.  The crash dumps have two different representations:

    1) a mapping of crash names to binary data blobs
    2) a mapping of crash names to file pathnames.

It has been a manner of gentleman's agreement that two types do not mix. However, as the two methods have evolved in parallel the distinction has become more and more inconvenient.

devise a method to unify the two cases
(Assignee)

Updated

3 years ago
Blocks: 1209526

Comment 1

3 years ago
Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/f2c34b5ac40efac7133b7bd132ed212201c4a100
Merge pull request #3022 from twobraids/dump_locations

fixes Bug 1212334 - disambiguate crash dumps being in memory or files

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.