Visual Studio 2019 (16.8.2) issue

[stephanh]

Hi,

is there any known issue with Live++ not working with Visual Studio 2019 version 16.8.2?
If i change anything in my source files, Live++ patches those successfully (according to log output). But the change is never applied to the binary. Debugger also doesnt catch breakpoints after the change anymore.

Tried full rebuild, removed .vs Folder, cleared Live++ AppData/Local Folder (symbols + logs).

No build settings where changed - worked before (although i cannot say if it was for 16.7.x or 16.8.1).

Thanks alot
-- Stephan

Environment:
- Live++ 1.6.1
- Visual Studio 2019 Professional (v16.8.2), v142 toolset, 64bit build
- Windows 20H2 (19042.630)

[Stefan Reinalter]

Hi Stephan,

Live++ should work as expected with VS 16.8.2.
Please make sure you are applying changes to functions that will be re-entered, and that your PDB settings (Linker -> Debugging) are set to /DEBUG:FULL.

[stephanh]

Hi Stephan,

Live++ should work as expected with VS 16.8.2.
Please make sure you are applying changes to functions that will be re-entered, and that your PDB settings (Linker -> Debugging) are set to /DEBUG:FULL.

Hi Stefan,



yes, Linker Settings are set to /DEBUG:FULL

Even if i add a simple printf("..") to my mainloop, the change never gets active. Adding a breakpoint there doesnt cause the debugger to break anymore.

---

Update:

Checked with older versions of Live++.

1.5.2 and 1.6.0 work, 1.6.1 shows the issue above. Same project, same settings - just swapped out the livepp directory.

[Stefan Reinalter]

Thanks for the update.
Can you confirm that the sample that ships with the 1.6.1 trial works for you?

For your project, could you please send us detailed logs?
The last bullet point in the FAQ has more info: https://liveplusplus.tech/docs/faq.html

Thanks!

[Stefan Reinalter]

As it turned out, the bug reported by stephanh was a regression introduced in 1.6.1, and has nothing to do with Visual Studio version 16.8.2.
The bug has been fixed in Live++ version 1.6.3 that was released a few minutes ago.

Thanks stephanh for the bug report!