[Lazarus] Debugging libraries which define generics.

[Donald Ziesig]

Hi All,

I have been working on some *serious* :-$ software libraries that 
declare generic subprograms and classes.

While debugging these I noticed:

 1. When single-stepping, the line being highlighted in the editor
    window is almost always (but not exclusively) one line *after* the
    line which is about to be executed.
 2. When the mouse hovers over a variable, the debugger (and program
    being debugged) frequently crashes with the error:
    "-data-evaluate-expression TCQPiece(ITEM)^" did not return any result.
    This is particularly annoying because it inevitably happens just as
    I am getting close to finding a problem and I move the mouse across
    the editor window :'(.

These problems do not occur when debugging non-generic code.

I am currently using Linux Mint 18 on an Intel core-i5 processor with 
gdb 7.11.1 (the Ubuntu version).  IIRC, I have had similar problems with 
Lazarus versions back as far as 1.2 and earlier versions of Debian, but 
I never had major generic software to debug until now.

I found reports of similar problems caused by line endings (Windows vs. 
Unix).  Is it possible that the code generated by generic specialization 
does not observe the OS-specific line endings and confuses gdb?  This is 
beyond my abilities to fix.

Any suggestions and/or further speculations will be welcome :-).

Don Ziesig


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20171215/222080db/attachment.html>