Gabriele Svelto

The files are taken from [this debuginfo package](https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Everything/x86_64/debug/tree/Packages/g/glibc-debuginfo-2.31-2.fc32.x86_64.rpm). One thing worth noting is that this file and other two from Fedora's glibc package exhibit this behavior and always did so...

@Gankra @luser I filed this as a follow up to the work on the stack walker.

> Is this a stepping-stone towards dealing with crashes involving non-canonical pointers? (Because it sure feels like it!) Yes! And much more, see a bunch of ideas we had [here](https://wiki.mozilla.org/Crash_reporting_improvements#Disassembly_in_the_stack_walker)

I ran a GSoC about this a couple of years ago (search for "helpful crash reporter" in [this page](https://wiki.mozilla.org/Community:SummerOfCode19)). There's useful stuff that can be done on the client side...

I filed a couple more bugs which somewhat overlap the existing ones: * Bug [1738651](https://bugzilla.mozilla.org/show_bug.cgi?id=1738651) - Flag crashes with potential bit-flips for server-side filtering This is about using a heuristic...

> n.b. this is not as trivial as it sounds because the in-memory executable code is not always identical to on-disk due to relocations being applied etc. The `chkimg` tool...

> Note too that in-memory libraries on Windows may differ from the on-disk ones because of Firefox's hooking of various functions. (I discovered this the hard way, thinking that I...

My only opinion on this is that the limits should be optional. I repeatedly bumped on Breakpad's when we started receiving dumps that went past one of them and it...

We also have a use-case for walking only the crashing thread: when we generate the output that we put in crash pings so that's something we'd also use. We've also...

Nice find!