remedybg-issues icon indicating copy to clipboard operation
remedybg-issues copied to clipboard

Better automatic PDB locator

Open x13pixels opened this issue 5 years ago • 3 comments

[casey] My recommendation would be to add "symbols" settings, honestly. It would have a few simple settings in it, like checkboxes for "search the system path" and "search the directory where the executable was" and stuff like that, for auto-hunting PDBs. It should also have a "symbol path" text box, or list, or whatever, where the user can specify paths to search for symbols. There should probably also be one that's like "project-specific symbol search path", which you would put below the working dir, and you'd save it along with the project?

Finally, the other really nice feature that you probably want is some way to set symbols per module. So like, if all else fails, the user can browse the module list, and say "hey this specific module right here, this is where to get the PDB from it, and by the way, give me a checkbox to override GUID matching so that I can force you to use a PDB for it even if it's wrong.

x13pixels avatar Apr 14 '19 00:04 x13pixels

+1

Is there currently a way to specify where to look for symbol files? The only way I could get the debugger to accept symbols for ntdll.dll is to put them inside the folder the RemedyBG executable is in.

spaderthomas avatar May 30 '22 20:05 spaderthomas

+1

bogez57 avatar Dec 04 '23 19:12 bogez57

Added global symbol search paths to 0.3.9.6. Leaving this issue open to add per-config symbol search paths and the loading of symbols for an individual module with the option to ignore mismatched debug identifiers.

x13pixels avatar Dec 10 '23 22:12 x13pixels