Skip to content
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

msys2-runtime-devel: missing debug info #4595

Closed
jeremyd2019 opened this issue May 13, 2024 · 4 comments · Fixed by #4600
Closed

msys2-runtime-devel: missing debug info #4595

jeremyd2019 opened this issue May 13, 2024 · 4 comments · Fixed by #4600

Comments

@jeremyd2019
Copy link
Member

jeremyd2019 commented May 13, 2024

msys2-runtime-devel-3.5.3-2 is missing msys-2.0.dbg. It also seems to be missing from msys2-runtime-3.4-devel-3.4.10-1, so I kind of suspect binutils, though I haven't looked into it at all.

@jeremyd2019
Copy link
Member Author

jeremyd2019 commented May 13, 2024

Looking at repo.msys2.org, it looks like msys2-runtime-devel got notably smaller here:
msys2-runtime-devel-3.4.2-2-x86_64.pkg.tar.zst 16-Dec-2022 08:11 5M
msys2-runtime-devel-3.4.3-1-x86_64.pkg.tar.zst 16-Dec-2022 22:23 361K

I can't believe nobody noticed lack of debugging info since then though. I know I was debugging the runtime since then. I must be missing something.

I did notice this because I wasn't getting any symbols in gdb for msys-2.0.dll today, for 3.5.3-2

@jeremyd2019 jeremyd2019 changed the title msys2-runtime-devel-3.5.3-2 is missing msys-2.0.dbg msys2-runtime-devel: misssing debug info May 13, 2024
@jeremyd2019 jeremyd2019 changed the title msys2-runtime-devel: misssing debug info msys2-runtime-devel: missing debug info May 13, 2024
@lazka
Copy link
Member

lazka commented May 13, 2024

I think this was removed in https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=99bb3e937a0fdbc1e3acbdc7cefb31e54a89a6ac and subsequently in msys2/msys2-runtime#125

So to have debug info we'd need to create it like for every other package I guess? options=(debug strip) Or do it manually to keep it in the same package.

@jeremyd2019
Copy link
Member Author

Hmm, I think I must have been using msys2-runtime-3.3 (on i686) when I was debugging the runtime lately.

jeremyd2019 added a commit to jeremyd2019/MSYS2-packages that referenced this issue May 14, 2024
Replicate the objcopy commands that used to work in msys2-runtime build
process.

also, don't strip msys2-runtime-devel.  makepkg's strip mechanism thinks
split debug files are binaries that need to be stripped, and debug files
with the debug info stripped are pretty useless.  msys2/msys2-pacman#52

Fixes msys2#4595
jeremyd2019 added a commit to jeremyd2019/MSYS2-packages that referenced this issue May 17, 2024
Replicate the objcopy commands that used to work in msys2-runtime build
process.

also, don't strip msys2-runtime-devel.  makepkg's strip mechanism thinks
split debug files are binaries that need to be stripped, and debug files
with the debug info stripped are pretty useless.  msys2/msys2-pacman#52

Fixes msys2#4595
@jeremyd2019
Copy link
Member Author

This is probably not the best place, but I noticed yesterday that windbgx (the ms store version of windbg) appeared to be making use of symbols from msys-2.0.dll when the debug info was not split (using the install.zip from the workflow on msys2-runtime), while it doesn't seem to handle the gnu debuglink thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants