Debug symbols for portable versions (Windows)

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
jb_wisemo
Moonbather
Moonbather
Posts: 56
Joined: 2016-01-27, 02:09

Debug symbols for portable versions (Windows)

Unread post by jb_wisemo » 2023-04-19, 20:18

For various tests etc. I run certain sites in the sandbox of a separate palemoon-portable instance. When this occasionally crashes, I would like to see something useful in a system debugger (WinDbg as this is Windows). However when I recently tried to do that with the normal debug symbols package I found that WinDbg did not recognize those symbols as matching the crashed browser. So I wonder what debug package to download.

:idea: Microsoft linkers now embed very exact identifiers for the specific run of link.exe that produced the crashed exe, dll etc., and Microsoft Debuggers don't allow much variation in the strictness of the check, so if the build scripts were run twice to produce the regular and portable binaries, they will need separate packages of PDB files, preferably organized as expected by DbgHlp.dll and its symbol loading libraries).

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35478
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Debug symbols for portable versions (Windows)

Unread post by Moonchild » 2023-04-19, 21:47

There is no difference. the normal windows binaries and portables are exactly the same. Using the symbols (with the correct architecture) should allow you to debug the crashes.
Note you may have more success using Visual Studio Community Edition. Older versions of WinDbg may not be able to read VS2022 symbol files.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked