Setting up debugger

[xaljox]

I've setup Codelite on multiple platforms. On a Macbook pro with M3 max processor under MacOs. On the same machine, under a VM parallels session were I run Windows 11, Arm64 version and on a Asus Windows 11 laptop with AMD Ryzen 9 processor.
With the mac version I'm not able to use a debugger. It states that the gdbi tself is Aarch64 and the target x64_x86, so that it can not debug an Aarch64 target, that is not that strang. But If I set the target explititly in the gdb to Aarch64, with either set architectur auto, or set architecture Aarch64, then it still does not work. Although with the auto, it says it sets the architecture to Aarch64, so it recognizes the target format. Note that I've codesigned gdb on the mac.
Next I tried to generate x64_x86 mac code, thus set some compile flags differently, but still not able to run the debugger. When invoking manually gdb, with the command line as shown in the output window, all seems fine, can set break main etc, but when invoking the run command, it all stops. It gives the message "Don't know how to run. Try "help target"".
On Windows (on the Mac) I can use the gdb debuger, when creating x64_x86 window targets with either gcc or clang. If I create an Arm64 windows debug image, I can not debug it with gdb. But the Arm64 target runs almost twice as fast as the x64_x86 images. Further I tried to get lldb_dab stuff running on windows plaform, both the windows VM on the Mac as Windows directly on the Asus. Both the lldb_dap directly as via the route with ccptools as described, do not work. The version with cpp tools complaines about MIDebuggerPath, but If I set that environment variable to where the lldb, lldb_dap, gdb applications are, the messages stays the same. I even copied lldb_dap to lldb_vscode, since that was the previous name. When starting a debug session the display changes and I get a pop-up from "CodeLite - Debug Adapter Client": "Failed to Launch debuggee".
With the created ccptools in the Debug Adapter Client, I got similar things, but with another message in the pop-up about the MIDebuggerPath.
So If anyone has suggestions, why the lldb_dab and cpptools are not working and on how to get that up and running, that will be nice. And also If it is possible to set up a working debugger environment when working natively on the Mac that would be nice, since that system is by far the fastest. Even the Windows VM on the mac runs faster as a native non sluggish AMD ryzen 9 laptop. Esspecially when running with Arm64 target images. So at the moment I can only debug with gdb on windows x64_x86 images. So in case of issues were I need a debgger, I need to switch to another platform, to debug the issue. I rather stay on the fastest platform, that is about 3x faster the a platform were debugging works. Plus putting over the changes to the other platform, also takes time.