Hello,

I am just getting used to RemedyBG and I am probably doing it wrong.

What I did:
- Compiled my program with debug info (I tried both /Zi and /Z7)
- Opened it in Remedy
- in "modules" it shows the symbols file and "symbols loaded"
- But in the Call Stack there are no infos regarding source files
and function names, so I can only see the Disassembly

Is there another step that I missed or is this an error?

Greetings,
Felix

Felix,

You aren't missing any steps. What version of RemedyBG are you running? I assume this is C or C++ code? What is the version of the Visual Studio compiler are you are using (or is this Clang)? When you hit F10/F11, does the program halt at the entry point or do you see disassembly?

--
George

I am using RemedyBG version 0.2.8.7

The code is C++ code and I am compiling with:
cl.exe - Microsoft (R) C/C++-Optimierungscompiler Version 19.16.27023.1 für x64
Which comes with Visual Studio Enterprise 2017 (Version 15.9.0).

When I press f10, the "[SUSPENDED] Program stopped at entry point" banner comes and I see the yellow arrow in the
Disassembly, but no source file comes up.

https://imgur.com/szFhE8z

I will try to find a minimal working example to send.

Greetings,
Felix

I have started with my code and stripped away everything that I thought that could cause it and found out the linker flag "/debug:fastlink" was responsible for remedy not finding the info. As I read about it on MSDN, fastlink keeps the source info in the .obj file and only references it in the pdb.

I hope this helps!

Ah, thank you very much for tracking that down! RemedyBG does not currently support /debug:fastlink. I'll take a look and see what it would take to support it.

Thanks much Felix.

--
George