Hmm... Do we want to be calling dumps with an incorrect number of records invalid? Or should we do header.records.iter().take(header.record_count), perhaps?

Both is better than crashing, but up to whoever looks at this what I should do. Both work.

Hmm... Do we want to be calling dumps with an incorrect number of records invalid? Or should we do header.records.iter().take(header.record_count), perhaps?

It's tricky, for sure. This crate has historically erred on the side of "get as much data as possible out of malformed minidumps", because our experience dealing with Firefox minidumps from end-users showed that we'd get dumps that were broken in all sorts of fascinating ways and getting something out of them was better than nothing. (Especially since Firefox exposes crash reports to enthusiastic end-users via about:crashes. There's nothing more demoralizing than having your browser crash, going to look up your crash report, and finding that it has no useful information because the crash broke things in a very specific way.)

Okay, I'll take the first header.record_count

Actually, why is there a record count anyways? Surely we already parsed some number of records and put them in header.records?

Ahhh, records is a fixed length array of records, and the ones past the record count is uninit (Well, presumably Default::default() because it's not wrapped in MaybeUninit, but semantically uninit).

Makes sense, avoids allocation. So if the record count is over 20, everything gets returned.

Rebased ontop of master to resolve the merge conflict. Other than that, left it untouched.

thank you so much!! https://twitter.com/Gankra_/status/1488254127633227780

awww that's made my day <3

Yep, I've not found any security vulns (other than DoS, i mean actual UB) in rust code through fuzzing

But I find a absolute ton of logic bugs and unexpected panics

The spiciest issues I tend to see are infinite loops in parsers and stack overflows (which kill a whole process, and catch_unwind will not save you >:))

I like to think I've been reasonably good at enumerating and testing corner cases (at least you're hitting assertions!) but yeah it's extremely hard to think of them all when you are literally writing "the thing that runs when a program has encountered an unrecoverable corner case" and at some point you get tired of coming up with contrived inputs that "surely will never happen in practice anyway, why am I even bothering".

Nice to have a machine look for them instead! 😸