[fpc-devel] Conditional Breakpoints using FPC and GDB

[Martin]

  On 13/08/2010 12:18, Graeme Geldenhuys wrote:
> On 13 August 2010 13:11, Michael Van Canneyt wrote:
>> Can you explain this ? As far as I know, there no member of the core team
>> that objects to having properties inspectable in the debugger ?
> I was obviously generalized a bit too much. If you really want me to,
> I can search the mailing list archive to find out who said what.
> Anyway, it was told many times before that inspecting a property with
> Getter and Setter methods may change underlying data - so the whole
> debugging of Properties are frowned upon.
>
> I'm simply stating that developers should know what they are doing,
> and that I have never seen a Delphi developer ever complain about that
> "possible data change" issue. It's only FPC developers that keep
> mentioning it.
>
IIRC that is mixing up 2 things. But in Graeme favour, likelihood has 
it, that others have mixed it up before: so this may have been said the 
way quoted (but not necessarily by people people listed)

IIRC there are several technical underlying issues (but I may be wrong): 
like not yet implemented to call functions from the debugger at all; and 
issues to represent the same symbol as getter and setter with the means 
of stabs/dwarf ?

The "accidental change" is more an argument, to have the function off by 
default.

And true, no one ever complains about having had that problem. Those who 
do have it are often beginners, they have no idea what it is, they blame 
it on their own code, and since they can't name it, they can't blame it. 
(IIRC that was my own experience too, a long time ago, in a galaxy right 
here)
[if any one feels the need to answer this last one: do it on fpc-other, 
or in private mail to me; or I get in trouble for having written this]

Martin