Activity for Claude Robitaille
-
Claude Robitaille created ticket #949
volume ID using GUID does not work in std::filesystem
-
The solution is simple, just upgrade gdb or gdbserver, or both, to version 12
-
My hunch tells me that the issue is related to the exception model (dwarf2 vs sjlj vs seh). Looking at the DLL that are included when I compile in shared more I am guessing that the model is seh. But what does gdbserver expects? Since seh does not exists 32 bits but sjlj does is it defaulting to sjlj^ How to determine ?
-
The work around is to use a VPN and connect from Canada. Well, I am in Canada and no luck. Does not work.
-
2 months later, still does not work. I guess compiling on Windows is not a thing; better switch to cross-compile from Linux
-
My hunch tells me that the issue is related to the exception model (dwarf2 vs sjlj vs seh). Looking at the DLL that are included when I compile in shared more I am guessing that the model is seh. But what does gdbserver expects? Since seh does not exists 32 bits but sjlj dies is it defaulting to sjlj^ How to determine ?
-
To help diagnose another issue I created a very simple helloworld program. If I compile it using -static and -static-libstdc++ -static-libgcc I am successful at compiling and executing my test program. If I try to compile without static, I can compile the program but fail to run it. Here is how I compiled x86_64-w64-mingw32-g++ hello.cpp -o hello Using this: /usr/bin/x86_64-w64-mingw32-objdump -p hello.exe | grep DLL I found that I needed to copy libgcc_s_seh-1.dll and libstdc++-6.dll at the same...
-
You should start to say where you are trying to compile from. mingw-w64 support compiling on Windows but as well as cross-compiling on Linux. In the case of Ubuntu you should start with the prebuilt mingw-w64 package. The tar file is for the case when you want to build mingw-w64 yourselves, which I doubt it is your intent.
-
I created a small test which behaves the same #include<iostream> #include <stdexcept> int main() { std::cout<<"Before the try block" << std::endl; try { throw std::runtime_error("Test exception"); } catch (...) { std::cout << "Catched the exception" << std::endl; } std::cout<<"After the try block" << std::endl; return 0; } And compiled using x86_64-w64-mingw32-g++ -static hello.cpp -static-libstdc++ -static-libgcc -o hello When running outside gsbserver, I get: Before the try block Catched the exception...
-
I created a small test which behaves the same #include<iostream> #include <stdexcept> int main() { std::cout<<"Before the try block" << std::endl; try { throw std::runtime_error("Test exception"); } catch (...) { std::cout << "Catched the exception" << std::endl; } std::cout<<"After the try block" << std::endl; return 0; } And compiled using x86_64-w64-mingw32-g++ -static hello.cpp -static-libstdc++ -static-libgcc -o hello When running outside gsbserver, Igt: Before the try block Catched the exception...
-
Hi, I am cross compiling my project on Ubuntu 20.04. I am doing a static link. When running my code on Windows exception handling work just fine. However, when running under gdbserver, I get this: terminate called after throwing an instance of 'helper::fileops::fileOps::fileNotFound' This happens even though I have a break point inside the catch block. I guess, somehow, gdbserver is interfering with the normal try/catch operation. I installed from the Ubuntu repository both mingw-w64 and gdb/gdbserver....
-
Make PID avaialble
1
