October 30, 2018 at 00:00 #22465
Just wanted to let you know that we have updated VisualGDB to run the Cygwin build of CMake using an alternate mechanism that does not trigger the problem. Please use this build: http://sysprogs.com/files/tmp/VisualGDB-188.8.131.524.msi
It also looks like as of v3.12, the Cygwin-based build of CMake would crash when trying to reload a project without restarting it:C++12assertion "0" failed: file "<...>/CMake/Utilities/cmlibuv/src/unix/core.c", line 185, function: uv_close0 [main] cmake 33156 cygwin_exception::open_stackdumpfile: Dumping stack trace to cmake.exe.stackdump
If you ever encounter that message, please right-click on the project in Solution Explorer and select “Reload CMake Project”. This will restart CMake and reload the project successfully.November 1, 2018 at 16:40 #22516
It seems that i missed the link you posted, it is already unavailable.
Please let me download it again.November 1, 2018 at 16:42 #22517
Sorry about that. Please download v5.4 Preview 8. It includes all the fixes from all previous builds.November 4, 2018 at 12:37 #22558
I’ve installed the v5.4 Preview 8.
I succeeded to load the project without errors.
The problem you mentioned happens every time i try to build the project.
On the build command i get following message:
Code model queried in 1483 msec
assertion “0” failed: file “/home/salex/CMake/Utilities/cmlibuv/src/unix/core.c”, line 185, function: uv_close
1 [main] cmake 47776 cygwin_exception::open_stackdumpfile: Dumping stack trace to cmake.exe.stackdump
Unexpected JSON message: expected Reply, got
System.Exception: Unexpected JSON message: expected Reply, got
at go1.m1[_InType,_OutType](_InType a)
at y22.m(String a)
at y22.x1(Hello a)
CMake exited with code 34304
System.Exception: CMake exited with code 34304
at v3.l(Object a, EventArgs b)
On rebuild command i got following message:
—— Build started: Project: Px4_WinGDB.vgdbcmake (failed), Configuration: Debug VisualGDB ——
VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe ../.. -G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″” in directory “/cygdrive/c/PX4/home/Firmware/VisualGDB/Debug” on local computer
/usr/bin/bash: C:PX4toolchaincygwin64bincmake.exe: command not found
Command exited with code 127
Arguments: -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe ../.. -G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″
VisualGDB: Error: Command-line action failedNovember 4, 2018 at 17:47 #22564
No problem, we can add a workaround to the first problem that will automatically restart CMake if it crashes during reconfiguration.
The second problem looks like you are using backward slashes in the path to GNU Make (configured via VisualGDB Project Properties). Please try using forward slashes instead and let us know if this solves the problem.November 6, 2018 at 07:31 #22588
I’m waiting for the fix.November 7, 2018 at 05:50 #22608
No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-184.108.40.2062.msiNovember 11, 2018 at 10:47 #22668
This version one is working. It started to build the program.
The next problem is that the VisualGDB executes bash.exe of Cygwin without login option.
VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer
This causes that some python scripts, which are activated from the CMakeList, cannot import modules (numpy).
I tried manually to do this, and bash.exe -l , should solve the problem.
Can i add this option in configuration, or the command is hard-coded in VisualGDB ?November 12, 2018 at 20:36 #22695
Yes, you should be able to customize the build command line via VisualGDB Project Properties -> CMake project settings -> Make Command.
You must be logged in to reply to this topic.