Ted Mielczarek
Ted Mielczarek
> even if it would, `rust-minidump` code will just fall back to other methods of unwinding when the CFI unwinder reports "there is no caller frame". It would be nice...
I hit this fairly frequently on my system. I have a script to restart synergys in this situation, but it would be nice if it didn't require that.
> Now this is would not be needed, if we extend the validity check to also be able to recognize JITed instructions. That requires another heuristic (e.g. proximity of the...
Nice sleuthing! Sounds like a question for @mstange .
> I am not sure whats the best way to do that, should I just generate a minidump from VLC and put that somewhere in the repository to use for...
> I would expect for this case for `module.debug_file()` to be `None` rather than an empty string so I'd like to see how does this work in practice, I suppose...
> I am not sure whats the best way to do that, should I just generate a minidump from VLC and put that somewhere in the repository to use for...
To get debug info without reinventing too many wheels I suspect the easiest path would be to use DWARF. If that's the case, then doing something that fits into existing...
I think this is fine, but knowing where to draw the line is pretty fiddly. It'll also be annoying to `cfg` out the disabled platforms in the higher-level crates that...
This issue came up in discussions the Firefox build team had with @alexcrichton last week. One thing that "build scripts as black boxes" makes difficult is caching build outputs with...