Hello

What debug information FP-compiler generates? To make proper expression evaluation, debugger should be aware of properties, otherwise result of the lines like this:

i := Memo1.Lines.Count; // there Lines and Count are properties

cannot be evaluated.

dmitry boyarintsev wrote

What debug information FP-compiler generates?

Stabs or Dwarf.

It is impossible to encode properties in stabs. In Dwarf you can in theory describe pretty much anything, but gdb does not yet support the full Dwarf specifications. I guess it would be possible already to add debug info for properties that simply map directly to a field, but other than that I'm not sure if there's much we can do at this point.

Jonas

functions, as well?
so i guess with no data about properties, in debug info, debugger should rely on available sources?

another question about debug information:

while debugging with gdb, i have found that object methods are 'mapped' to the debugger (or debug information?) as functions with additional parameter 'self' (what they actually are),

so let's say, i have an object m: TMyObject with method procedure MyMethod;

while gdb, does not understand the syntax, m.MyMethod, method still can be called with TMYOBJECT_MYMETHOD(m) call.

can name collission to happen? if i also have function in the code, named like procedure TMyObject_MyMethod(a: TMyObject), so it's name would match (?) for the debugger with MyMethod ?

I hope my question is clear :)

------ Here's the code

type
  TMyObject = class
  public
  procedure MyMethod;
  end;
procedure TMyObject.MyMethod;
begin
  writeln('My method object');
end;
procedure TMyObject_MyMethod(m: TMyObject);
begin
  writeln(m.ClassName);
end;
procedure TMyObject__MyMethod(m: TMyObject);
begin
  writeln(m.ClassName, ' **');
end;
var
  m : TMyObject;
begin
  m := TMyObject.Create;
  m.MyMethod;
  TMyObject_MyMethod(m);
  m.Free;
end.

------ Here's the debugger output

(gdb) info functions
All defined functions:

File main6.pas:
void PASCALMAIN(void);
void TMYOBJECT_MYMETHOD(TMYOBJECT);
void TMYOBJECT__MYMETHOD(TMYOBJECT);  // TMyObject method?
void TMYOBJECT__MYMETHOD(TMYOBJECT);  // TMyObject method?

------

is there anyway for debugger to understand which of the procedures is actually TMyObject method?

Thanks.

A property is not only reading but might be writing also (or only).

Marc

i know Marc, but the purpose is to make expression evaluation.

while setting property is procedure, i can't think of any expression that uses it. But of couse, it might be usefull to know how to set properties (directly member of class, or a method)

i guess, that property information is also available at .ppu files

Unfortunately, a debugger doesn't have that information.

Marc