Mailing lists / lazarus / 2018-12
2 messages · 2 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi All,
I use Lazarus fixes_2_0 and FPC fixes_3_2 (OS_TARGET=win64 CPU_TARGET=x86_64). Which is the best Dwarf selection for this combination and FPDebug?
Gabor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Lazarus_FPDebug_Dwarf.png
Type: image/png
Size: 7983 bytes
Desc: not available
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20181214/359a68b6/attachment.png>
Dwarf 3 should be perfectly fine. And yields better results (upper/lower case of identifier names are preserved).
However with Dwarf 3, ansistrings may be displayed as array of char. This is fixed in trunk, but not merged to fixes.
IIRC With Dwarf 2, in both trunk/fixes Ansistring are PChar. And this can not be fixed, as for Dwarf 2 fpc writes the same debug info for ansistring and pchar.
IIRC WideStrings are always PWideChar (with any combination). And ShortStrings are embedded in a record in fixes, but shown correct in trunk.
