[Lazarus] lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

[Martin]

On 15/09/2011 10:33, Graeme Geldenhuys wrote:
> On 14/09/2011 22:06, Martin wrote:
>> while ansistring pose a general problem, using shhotstring, stabs does
>> the job. (fpc trunk / gdb 7.3-2 / win 32)
>>
>> VarString15 starts with "T15"
>> -data-evaluate-expression VarString15[2]
>> STABS: ^done,value="49 '1'"
>> DWARF: ^done,value="53 '5'"
>>
>> dwarf3: ^done,value="84 'T'"
>
> This inconsistent output from GDB has bitten me before! I struggled for
> hours debugging my code, just to find out GDB doesn't handle FPC strings
> correctly.  Since then my GDB usage is limited to breakpoints and
> stepping, and tiOPF's logging is for analysing the "real" data values.
Well as I said before (and well it your choice I accept it, but),  
statement like this make it look like:
You seek the few error, in order to abandon everything.

I agree, error like this, make it incredible hard for newcomers. But 
from all I know, you aren't a newcomer?

By now, you should know the can-do and con-not-do, and you should be 
able to use accordingly. (e.g. watch the entire string, instead of an 
index / or add  1 to the index yourself)