Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2014-07

GDB Logging options

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Justin Smyth

Hi All,

With the recent changes I can now compile for my arm embedded target using lazarus and can get lazarus to use my EABI GDB to connect to openOCD V8 OK , is there a way I can see what commands are sent to GDB when lazarus starts it up ? I want to check to see if my changes in the class I've added are working and what is sent to gdb so I can check against what I would sent from a cmd prompt.

At present I start up OpenOCD V8 in a cmd prompt and when lazarus starts the EABI GDB I can see the connection occur in OpenOCD , So I am getting some where now.

Thanks to Sven for your help and Michael Ring who with out his help I would be up the creek with out a paddle. ( and also martin for his help in getting my own class working for gdb )

Kind Regards

Justin Smyth

Earlier message 23 lines
-----Original Message----- From: Sven Barth [mailto:] Sent: Thursday, 17 July 2014 6:24 AM To: Subject: Re: [Lazarus] Compiler Options On 16.07.2014 22:00, Mattias Gaertner wrote: > On Wed, 16 Jul 2014 21:25:49 +0200 > Sven Barth wrote: > >> [...] >> It's likely better to rely on the system.ppu... :/ > > Some users installed fpc with system.ppu and no classes.ppu. That's > why the test was added years ago. How did they manage that?! O.o Regards, Sven --

Reply by email

Martin Frb
to Justin Smyth
Justin Smyth wrote 10 lines
Hi All, With the recent changes I can now compile for my arm embedded target using lazarus and can get lazarus to use my EABI GDB to connect to openOCD V8 OK , is there a way I can see what commands are sent to GDB when lazarus starts it up ? I want to check to see if my changes in the class I've added are working and what is sent to gdb so I can check against what I would sent from a cmd prompt.

http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session

you need either of those. first one shortens long lines (gdb response of all lines in a unit ran be very long)

--debug-log=LOG_FILE --debug-enable=DBG_CMD_ECHO

--debug-log=LOG_FILE --debug-enable=DBG_CMD_ECHO_FULL

add

DBG_STATE to see the state of the IDE debugger

DBGMI_QUEUE_DEBUG to see which commands belong together.

Install the laz_ide_logger (or similar) and toggle them while the IDE is running

Reply by email