x86

Feature type

Quality of life

Describe the feature

I would like to be able to use relative paths in the launcher settings file to point to x32dbg.exe and x64dbg.exe respectively. I've already tried editing the file manually and assuming my implementation (.\/\//) isn't wrong, the launcher seemingly refuses the use of relative paths.

It would be nice when the virtual machine is fullscreened if the scale automatically adjusted to make it as big as it can. Sorry If this is hard to understand

Sometimes it is useful to know where a function was called from. We currently don't display this information.

如：xxx app + www.xxx.com

不要在此issue里面提各种问题，谢谢配合。

While the test_suite presented in #589 does work, it is still pretty simple and can be improved and enhanced.

• Add tests for gnutils and coreutils.
• Add necessary utilities so more complex programs can be compiled from sources.
• Integrate CMake, so one could write something like make validate and the subset of test that is deemed necessary (for example everything with min t

Describe the bug
In Linux when the engine loads, it detects that there is EFX capabilities but then states that EAX 2 is out of the question.

Expected behavior
shoudln't EAX usage be replaced by EFX usage? and if so maybe this should be indicated when the sound is loaded, isn't it?

BugTrap error report

SOUND: OpenAL: enumerate devices...
SOUND: OpenAL: EnumerationExtensi

It's currently always using mov rAX,[moffs] but if it fits in an i32, it's shorter to use mov rAX,[m] with a modrm byte.

The generated mov() methods would need to be updated. This is what the generated C# code looks like:

			if (dst.Value == Register.RAX && Bitness == 64 && src.IsDisplacementOnly) {
				code = Code.Mov_RAX_moffs64;

An extra check would need to be adde