I’m not 100% whether it’s the only way, but afaik the API used on the Windows side relies on pulling the symbols from a .pdb file. Alternatively, you can dump the offsets and bases, and make a tool for automatically matching it to symbols on your dev machine (I believe this is not done in the JUCE function although it is possible).
Yes the .pdb may optionally contain some information, but it’s not like that information can’t be reverse-engineered anyway if it’s worth it
It’s still as illegal (if you state so) to reverse-engineer the .pdb