@AT

I'm facing regression in Delphi 12 which blocks me in debugging EMS Server packages. Debugger does not stop at any breakpoints in source code; debugger does not display any symbols in CPU Debug View when execution is stopped in the package, After short investigation I found that local debuggers (Win32, Win64) do not load debug symbols for dynamically loaded packages via LoadPackage function. Issue is reproduced with Delphi 12 SP1 and is not reproduced in Delphi 11.3.

I'm trying to debug shared library loaded by Linux application. I need to attach debugging session to existing process on remote machine. However, ""Run"->"Attach To Process" configuration form is empty for any debuggers except Windows debuggers. Delphi documentation refers that I should select Connection Profile for remote debugger; however, this field is not available I choose Linux 64-Bit debugger, or any other non-Windows debugger in "Attach To Process" configuration form. I use Delphi 11.4 and 12 IDEs both of them have the same behavior. "Attach To Process" configuration from looks like at attached screenshot. Does anyone have experience with experience with attaching to the Linux process debugging in Delphi/RAD Studio IDE?

Hello Lars, I'm absolutely unsure that gdb.exe must be installed on the development host. Starting 11.3 Delphi support only LLDB: https://docwiki.embarcadero.com/RADStudio/Athens/en/11_Alexandria_-_Release_3#Debuggers

Hello Lars, Of course, I have read that; however it works well for local and remote Windows Debugging only. Ok, let me explain the issue in more details. II have environments developing Delphi applications for Windows, MacOS and Linux for long time. They are more or less stable for normal application development and debugging. However, I can use remote debugging for Linux and MacOS only using "Run Debug" option. "Launch Process" and "Attach to Process" do not work with with MacOS and Linux debuggers. I just found that RAD Studio documentation in this area is unsynchronized and confused: Two documents below describe how to set-up remote debugging including "Attach to Process" and "Load Process" with remote Linux and MacOS. https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Attach_to_Process https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Attaching_to_a_Running_Process However, the https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Debugging_Multi-Device_Applications says "Attachment to a running process is not supported for the Embarcadero Linux 64-bit Debugger, Embarcadero iOS Device 64-bit Debugger, Embarcadero Android 32-bit Debugger, Embarcadero Android 64-bit Debugger, Embarcadero macOS 64-bit Debugger, and Embarcadero macOS ARM 64-bit Debugger.". This document also confirm that "Load Process" debugging functionality works on Linux and MacOS. However, in my environment the "Launch Process" displays error message Unable to start LLDB kernel: "Unable to find program, gdb.exe", which does look weird for me.

Thank you havrlisan for you comment. However, my original question is a first post in this thread. I'm wondering if anyone uses "Attach to the process" debugger functionality with non-Windows applications and does anyone have the similar issue as I described in that post.

I'm wondering if anyone debugs non-windows application 🙂

My list of preferences: arm64 compiler for Linux Enable Generic functions (pure functions/procedures, but not members of classes) Ability to declare external functions without pointing library names (to simplify writing libraries for Linux applications (both, shared and statically linked) Static Code Analysis build-in Improve "Refactor" functionality [Need to think more...]

Hello Remy,, Of course, I have configured Connection profile already. Regular debugging with "Run", "Run with parameters...", "Load Process..." work well with Linux. The problem is only with "Attach To Process" debugging.