Ted Mielczarek

> If there's some macro or whatever to get the version from the Cargo.toml, perhaps the "post release" commit should update everything to NEXT_VERSION-alpha. You're already using one :slightly_smiling_face: :...

I like [`cargo-release`](https://github.com/crate-ci/cargo-release) for automating the whole version bump-tag-commit-version bump + `cargo publish` cycle. I don't think I've tried it with a workspace like this, so it's worth verifying that...

It's an excellent thing to have because you definitely run into situations where something looks broken but you're pretty sure it was fixed at some point, so you can verify...

Huh, interesting! Is that supported by Mozilla's `dump_syms` implementation? I assume that if this was in use in crash-stats it would have shown up in @Gankra's output-comparison testing. For prior...

This is a stack overflow in pure Rust code, right? So it'd be hitting the guard page that `std` adds there.

Fascinating! My guess is that Windows CE was different enough that there wasn't any real pressure to share an implementation, so they just borrowed the form but made different implementation...

@Gankra just something that popped into my head thinking about 1.0 API stability. I don't think this is critical for Mozilla's usage, since crash-stats is not accepting full memory dumps...

> I had to remove one `repr(packed)` from a type but since we read with Pread I don't think it was actually doing anything? _Maybe_ making it easier for Rust...

> [Check if the binary around the crash matches what we ship](https://bugzilla.mozilla.org/show_bug.cgi?id=1274628) This should be doable given that the symbol server also hosts the matching binaries. As it turns out,...

> This one is about doing something like `chkimg`. One way to do it without downloading the whole executable would be to add an `INFO CHECKSUM` to the .sym files...