• Basile B. (20/20) Aug 27 2021 Select a custom executable, that's been compiled with dwarf info
• Imperatorn (2/7) Sep 01 2021 Cool. Great job
• Basile B. (17/25) Sep 06 2021 Lazarus debugger can do that too.

Basile B. <b2.temp gmx.com> writes:

Select a custom executable, that's been compiled with dwarf info 
(e.g -g).
this custom executable has not to be related to the focused 
project.

![](https://i.imgur.com/6XCONPS.png)

it even has not to be written in D. For example here I debug an 
obscure program written using an obscure home-made language

![](https://i.imgur.com/2ZWVD1K.png)

(_first time using images since cybershadow added md support so_ 
[_better res_](https://i.imgur.com/OYLmu8q.png) _here as I dont 
know how to make a clickable thumbnail_)

as long as dwarf info are there this should work.

Breakpoints will have for effect to load the source file. If the 
source file is loaded in dexed before debugging and breakpoints 
are put before pressing the power button, they will be handled.

Signals will be handled too. they give a dialog on encounter. It 
proposes to cancel the break (i.e continue) or accept it to do 
things such as: add more bp, evaluate expressions, change the CPU 
register values, etc.

(note: **LINUX ONLY**)

Imperatorn <johan_forsberg_86 hotmail.com> writes:

On Friday, 27 August 2021 at 17:34:34 UTC, Basile B. wrote:
 Select a custom executable, that's been compiled with dwarf 
 info (e.g -g).
 this custom executable has not to be related to the focused 
 project.

 [...]

Cool. Great job

Basile B. <b2.temp gmx.com> writes:

On Wednesday, 1 September 2021 at 17:08:30 UTC, Imperatorn wrote:
 On Friday, 27 August 2021 at 17:34:34 UTC, Basile B. wrote:
 Select a custom executable, that's been compiled with dwarf 
 info (e.g -g).
 this custom executable has not to be related to the focused 
 project.

 [...]

 Cool. Great job

Lazarus debugger can do that too.

1. Execute > Parameters > Host application
2. in the field set the custom app
3. run

this works because in theory you can debug a dll written in 
ObjFPC but that will be used by a "foreign" program. The feature 
is not explicit but that just works ;)

![](https://i.imgur.com/JqJVRI6.png)

And Qt creator of course allows the same

![](https://i.imgur.com/g6AiGyR.png)

using Debug > Start Debugging > Debug An External Application.

In fact resricting a GDB gui to a single language makes no sense.

1. The source language does not matter or it is automatically 
selected
(GDB only knows a few variation: C C++ Pascal Fortran etc.)
2. it's dwarf in all cases...