Korcan Karaokçu

Tested with a simple, infinitely looping rust binary with debug info. `.format_string().strip('"')` doesn't fix anything, GDB can't read the path var at all, printing the variable gives ``

I've solved the void pointer issue with changing this code In ScriptUtils `void_ptr = gdb.lookup_type("void").pointer()` to `void_ptr = gdb.lookup_type("u8").pointer()` It works if we use u8 instead of void. But again,...

Here's something interesting, none of these issues appear if the target is compiled in release mode

Considering all other issues, such as not being able to read string variables and all. I think the best solution would be to make GDB act like it's a release...

I can't seem to reproduce this on my end. Can you share your specs and the name of the application you are using pince with?

I've switched to my Fedora virtual machine and tested it, you are absolutely right! That's apparently a Qt bug related to gnome: https://gitlab.gnome.org/GNOME/mutter/-/issues/2715 There's not much to do since it's...

> All I'm saying is that while this likely is a Gnome bug, it doesn't seem to be covered by that particular Gnome issue. Yeah, that was the first one...

Any updates with this one? You can use the AppImage we provide in the releases to test

It's in the roadmap. Scripting and assembler are already available but they are not integrated into GUI yet. Libpince engine is the scripting support and it actually is the next...

Open a console in pince root folder and activate the python env, then launch python with root privs like `PINCE.sh` does. So, in short: ``` . .venv/PINCE/bin/activate sudo -E --preserve-env=PATH...