On 13/10/2010 18:08, Michael Van Canneyt wrote:
I don't the problem is not the data type char, but that somewhere in
the debugger tool chain (from lazarus tool-tips front end to the gdb
backend using the fpc generated debug info) the assumption is used
that pascal strings are indexed starting from 0 instead of 1.

Probably that is just how gdb works by default.


GDB being C-biased, that is quite likely the cause. Means that the debugger interface must work around it.
actually, I think in dwarf 3 the lower bound can be defined (and from a search in fpc sources, it may even be done...); but I couldn't get dwarf 3 results to work at all...

Martin

--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply via email to