I am porting code to modern compilers and unfortunately encountered a subtle segmentation fault when an FFI function was invoked from Rust to C++. The stacktrace showed that after the transition to C++, the first argument provided from Rust magically disappeared which misled C++ to use wrong arguments. The code was somewhat private so I ..
Category : abi
Can’t call a class method using libffi library working with function calling convention. On x86, it turned out to write code using _asm rates, transferring that code to x64 no longer works since there is a different system for passing parameters to a function. There is a description in the article https://docs.microsoft.com/ru-ru/cpp/build/x64-calling-convention?view=msvc-160. I want to ..
The common explanation for not fixing some issues with C++ is that it would break the ABI and require recompilation, but on the other hand I encounter statements like this: Honestly, this is true for pretty much all C++ non-POD types, not just exceptions. It is possible to use C++ objects across library boundaries but ..
I have a piece of legacy C++ code which lives in a library and is loaded as DLL by an application: // Foobar.h (old) struct Foobar { const char* foo; const char* bar; int apple; int banana; }; // Foobar.cpp (old) void func(Foobar* ptrFoobar) { cout << ptrFoobar -> foo << endl; cout << ptrFoobar ..
I have the following file foobar.cc: struct Foo { virtual int do_something() const = 0; }; struct Bar : public Foo { virtual int do_something() const override { return 1; } }; Bar bar; When I try to build a shared object out of it like so: g++ -shared -fPIC foobar.cc -o foobar.so nm foobar.so ..
For a personal project, a raspberry pi-controlled guitar pedal, i’m creating a small library. This library contains a bunch of classes specifying the the function of several types of effects. For this I have an Effect base-class that every effect inherits from, together with an EffectFactory base-class that will create sequences of effects based on ..
I am creating a client server architecture where I use c++ as my backend and QML/c++ as my frontend.. I share commomn c++ structures in a common library that make up the data that is passed between the client and server through it’s API. So now if I have a structure like this in the ..
I think it’s impossible or very dangerous to send pointer / reference to dynamic loaded library from another compiler or ever another languages like C#. And I want to find proofs, but C++ standard documentation is pretty huge. I think null terminated string will work fine, but how about std::string, or maybe string_view? Source: Windows ..
I have the following interface class: class __attribute__((visibility("default"))) Base { public: Base() = default; virtual rtype method1() = 0; virtual rtype method2() = 0; ··· virtual rtype methodN() = 0; } And the following child class: class __attribute__((visibility("default"))) Child { public: Child() = default; virtual ~Child() = default; virtual rtype method1() { ··· } virtual ..
For some reasons I need to link an executable (in Linux) which has object files compiled by different C++ compilers and versions. I use g++ and clang (9, 10 and some older ones). May occur any compatibility issues in this scenario? Thanks Source: Windows Que..
Web Development Company
Cazare Cristian Brasov
Recent Comments