Lazarus

Using the Lazarus IDE => Debugger => Topic started by: nanobit on October 31, 2018, 08:13:44 pm

Title: GNU debugger (with fpdebug)
Post by: nanobit on October 31, 2018, 08:13:44 pm

On win32, my current setting is dwarf 3 und compile unoptimized,
I have this set for all packages and the using project.
I toggle sometimes between  "GNU Debugger (gdb)" and  "GNU debugger (with fpdebug)".
Only in the latter case, I cannot step through Lazlogger functions (eg. GetDebugLogger), but get this error message:

[Window Title]
The debugger experienced an unknown condition

[Content]
Press "Ignore" to continue debugging. This may NOT be safe. Press "Abort" to stop the debugger.
Exception: EAccessViolation with message "Access violation"
Context: TFpGDBMIDebuggerCommandLocals. State: dsPause

  $00E6FE04 line 758 of fpdmemorytools.pas
  $00E6AF40 line 683 of fppascalbuilder.pas
  $00E6A72A line 897 of fppascalbuilder.pas
  $00E6CDEC line 919 of fppascalbuilder.pas
  $01272B7D line 288 of fpgdbmidebugger.pp
  $0127276F line 234 of fpgdbmidebugger.pp

[Abort] [Ignore]

Is there an easy remedy for this?

Title: Re: GNU debugger (with fpdebug)
Post by: Martin_fr on October 31, 2018, 09:06:31 pm

The trace is while reading local var for the local window.
But this will happen, even if the locals win is closed. Unless you also "power off" the history window.

Or, maybe in the run menu, you can try to select "Display gdb intstead of fpdebug...".

Title: Re: GNU debugger (with fpdebug)
Post by: nanobit on October 31, 2018, 09:33:45 pm

Oh, "Display gdb intstead of fpdebug watches" is really nice, and I still get the better string view:)

Title: Re: GNU debugger (with fpdebug)
Post by: Martin_fr on November 03, 2018, 11:43:48 pm

Fixed the crash. Good catch.
That crash could happen as soon as any locals had a structured variable (class, record), including self.