Advance CMake build reporting delay and issues

[kurt]

• VisualGDB 5.3R8
• VS 2017
• Using Advanced CMake + ninja

Issue 1:  Linker errors are not reported in [Output] or [Error List].

• All I get is “FAILED” in the output.
• If I don’t use Advanced CMake, then the linker error does get reported.
• With Advanced CMake, my current workaround is to enable “VisualGDB diagnostics logging”.  The linker error will be there.

Build output:

Configuring done
Generating done
Code model queried in 31 msec
VisualGDB: Run “ninja ” in directory “/build/helloWorld/VisualGDB/Debug” on blah@192.168.1.2 (SSH)
[0/2] Building CXX object CMakeFiles/i…/source/helloWorld.cpp.o
[1/2] Linking CXX executable bin/helloWorld
[2/2] Linking CXX executable bin/helloWorld
FAILED: bin/helloWorld
: &&  .. <I’ve truncated it> … linux.2/VisualGDB/Debug/bin/helloWord
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Diagnostic:

Searching for active configuration for build.linux.vgdbcmake…
Trying fast lookup…
Found! Configuration name = Debug
[+70753] ReportQueuedMessages()
[+0] ReportQueuedMessages() – 1 queued messages
[+69] ReportQueuedMessages() – 10 queued messages
[+18] ReportQueuedMessages() – 9 queued messages
[+0] ReportQueuedMessages() – reporting: source\helloWorld.cpp:54 – undefined reference to `blah’ (build.linux.vgdbcmake) <– NOT REPORTED!
[+0] ReportQueuedMessages() – 8 queued messages
[+4] ReportQueuedMessages() – 7 queued messages
[+3] ReportQueuedMessages() – 6 queued messages
[+7] ReportQueuedMessages() – 5 queued messages
[+3] ReportQueuedMessages() – 4 queued messages
[+2] ReportQueuedMessages() – 3 queued messages
[+3] ReportQueuedMessages() – 2 queued messages
[+3] ReportQueuedMessages() – 1 queued messages
[+0] FlushToTaskList()
[+0] FlushToTaskList() – done
Searching for active configuration for build.linux.vgdbcmake…

Issue 2: Rebuild takes longer than necessary.

My project consists of 3000+ files.  When building, I don’t see any activity in the Output log whenI do not set the “-v” flag for ninja.  There should have some output (if compiled outside of vgdb).

• It’s either ninja or VGDB is not flushing the output.

Then, I can see that the output is already built, and there are CPU activity (build is really done), but vgdb is still stuck at “building”.  I have to wait like 5-10 minutes for nothing for it to return.  If I cancel the build, I will see “VisualGDB: Sending Ctrl-C…” stuck for minutes.

• Another flush issue?

Looking at the diagnostics, there’s tons of messages stuck somewhere:

Found! Configuration name = Debug
Searching for active configuration for build.linux.vgdbcmake…
Trying fast lookup…
Found! Configuration name = Debug
[+254281] ReportQueuedMessages()
[+0] ReportQueuedMessages() – 1 queued messages

 

Is there an option to manually flush the output, or set it to flush every 15 seconds?

[support]

Hi,

Thanks for the detailed description. Please try our latest build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2075.msi

If the problem persists, please share the ENTIRE build log (you can do find-and-replace to switch out meaningful project/file names with random names, but we will need to see the order of internal VisualGDB messages in order to understand what is going on).

As another quick check, please try running Ninja manually via SSH and confirm that it produces the output consistently and doesn’t freeze.

[kurt]

Quick update:

• New version didn’t help (but I just installed and ran … I didn’t re-create the project. I’m not sure if I’m previous hack to add “Ninja” in the XML messes up anything).
• Manual call to ninja via SSH works fine, no stalling.

It actually works fine outside of Advanced CMake.

Anyway, I’ll gather the detailed log.  Be right back …

[Author]

Posts