On 21/11/2018 17:34, Michael Ring via lazarus wrote:
Hi Martin, thank you for the detailled answer.
I like your idea of creating Id's for debugger configurations and as I
want to go step by step (and I have great respect of 130kBytes of code
in TEnvironmentOptions) I wanted to start small and
Hi Martin, thank you for the detailled answer.
I like your idea of creating Id's for debugger configurations and as I
want to go step by step (and I have great respect of 130kBytes of code
in TEnvironmentOptions) I wanted to start small and grow as I go. I
am tempted to give the full
Hi,
On 2018-11-20 23:44, Michael Ring via lazarus wrote:
What is the best way to implement this project based override, I guess
I can do the coding myself as I have also created my own debugger for
JLink, but I do not know how to do this debugger switching in the
proper 'Lazarus' way.
I
On 20/11/2018 22:44, Michael Ring via lazarus wrote:
There is only one issue I see at the moment, the debugger is a global
setting, afaik I cannot change the debugger configuration based on a
project.
The problem is that for debugging arm I will have to use
arm-none-eabi-gdb, for pic32 I
Hi!
Since a while I am using lazarus not only to edit/compile projects for
embededded controllers, but also debugging now works very nicely.
There is only one issue I see at the moment, the debugger is a global
setting, afaik I cannot change the debugger configuration based on a
project.