Debugging Symbols

Development Programming & Scripting C++
#1

Hi,

Would it be possible for debugging symbols for core modules to be distributed with launcher builds, or, maybe just via the GitHub repository or forums?

Whilst it is possible to build and debug the engine using the GitHub source, there are a few cumbersome problems:

  • The project’s engine has to be switched from the launcher build to the local build folder, and the game/engine projects are merged into one massive solution
  • Every time there is a new release, the source + optional dependencies have to be downloaded again and the engine has to be recompiled
  • Engine code seldom needs to be altered, so my use case for this is working on game code, and quickly needing to see where I dun goofed to make the engine crash so I can fix it

It would be much easier to point Visual Studio at a selection of included symbol files and the GitHub source.

I’d be interesting in the following editor symbols:

  • UE4Editor-Core
  • UE4Editor-Slate
  • UE4Editor-SlateCore
  • UE4Editor-InputCore
  • UE4Editor-RenderCore

That’s quite a small list, and there might be a couple more common ones to add there. At least with the core symbols, no-mans land call stacks can be avoided while working on game code :slight_smile:

2014-07-29-7r227L.png
2014-07-29-7r227L.png871×954 52.3 KB

Thanks!

Alan

#2

I am also very interested in - at least - having the debug symbols for all engine+editor binaries.

Maybe add a switch in the launcher for non-devs to avoid downloading stuff that won’t be useful for them. But for devs symbols are really needed.

I also discovered the “DebugGameEditor” is actually NOT a real debug build. It is a release with debug info, which is not the same thing at all - meaning 50% of the time VS debugger will just skip some lines, or not go inside a function (very frequent with UE functions). Is it possible to have such a thing as “real” non-optimized debug ?

Thanks