New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust cross compiling using MinGW #594
Comments
I believe this is because we do not (yet) support DWARF in PE. |
Also when I use the .dll file without stripping I got this result with the sentry-cli command,
I have the feature |
Another problem here is also that the file is missing a |
Yep, but why is it missing? I only cross compile using Rust and MinGW. |
The issue is similar with #354, wdyt? |
Any news, please? |
It might have something to do with the mingw tools. The issue you linked above is using Another member of our team is trying to reproduce this. |
Ok, thx, if you need any help please keep in touch with me. |
The team has had a look at this and we were able to reproduce this, though did not find a proper way to make this work. In general we appreciate community contributions related to MinGW very much, but we do not actively support it, neither for the native SDK nor for Rust. MinGW in general is a very broad target with a diverse set of tools. In general we need debug files/formats in their "native" container type. Which means that PDB needs to be in a PDB file, and DWARF needs to be in either an ELF or Mach-O container. We do support using ELF/DWARF debug info in combination with a PE executable though. |
So you mean I need to convert the dwarf debug info to PDB? |
Either convert the whole debuginfo to pdb, or just make sure that the DWARF is in a container format that is appropriate for it, like ELF. |
Is it normal that after I used the ELF debug information format, I'm also missing the Debug ID?
|
I don't know how to read 😄 , everything is written here, https://docs.sentry.io/platforms/native/guides/minidumps/data-management/debug-files/identifiers/#gnu-build-identifiers. But after doing that, I got the identifier for the executable, such as,
But when I used the command |
Hi,
I cross compile my code from Mac OS to Windows using MinGW and the target
x86_64-pc-windows-gnu
.I use the
RUSTFLAGS="-g -C opt-level=3"
to generate debug information when being in release mode.Then, I run the command,
After that, I use to have the
library.debug
file containing all the debug information but when I want to check if it is usable by Sentry usingsentry-cli difutil check library.debug
I have this result,Do you know, what I can do to get the debug information send to Sentry correctly to be able to map it with my library?
The text was updated successfully, but these errors were encountered: