Code instrumentation plz

[hinst]

Is there a free tool for Object Pascal code instrumentation which can for example insert calls like:

Code: [Select]

procedure TFffuuu.Meow;
begin
  NotifyProcedureEntered('TFffuuu.Meow'); // <- tool inserts call here 
  ... // method body here
  NotifyProcedureExited('TFffuuu.Meow'); // <- tool inserts call here
end;

any insight appreciated

[marcov]

Afaik the profiler settings insert something like that. But that will be address based, so you'd need a map to transform it back.

[BigChimp]

See also
http://wiki.lazarus.freepascal.org/Profiling
for the various options

[skalogryz]

Not sure, if it's for profiling task in the end.
Feels like like auto releasing mem approach

btw, it should definitely wrap it into try...finally section

Code: [Select]

procedure TFffuuu.Meow;
begin
  NotifyProcedureEntered('TFffuuu.Meow'); // <- tool inserts call here 
  AllocStuff; //ref counting?
  try
  ... // method body here
  finally
    DeallocStuff; //ref counting?
    NotifyProcedureExited('TFffuuu.Meow'); // <- tool inserts call here
  end;
 
end;


[hinst]

I find all profilers not satisfying, I want my own profiler, I only need to automate code instrumentation

[skalogryz]

I find all profilers not satisfying, I want my own profiler, I only need to automate code instrumentation

Not invented here syndrome?

Check Cody package. Maybe it has something useful.

I'm specifically referring to explode / add "with" block. It feels like something similar to what you need. So with a small patch, you could extend Cody to do what you need.

[hinst]

I rather have "everything sucks" syndrome, and not without a reason

[BigChimp]

Interesting. Have you actually looked at the referenced code or do you have a very precise crystal ball

I would concur with skalogryz' thrust though: perhaps it's easier to fix something that sucks rather than have to write everything from scratch. Your improvements may also help other Lazarus/FPC devs.

[hinst]

Well, I currently need profiler which would work for Delphi code as well. I tried two profilers for Delphi and I am not satisfied with them because they provide useless information (at least I could not make any sense of it). They both do not instrument code.

I can't use FPProfiler for this for the following reason: it uses fcl-passrc to parse sources. I already tried using fcl-passrc to parse my sources, it can parse only 100 of 600 units........ yesss....

[BigChimp]

Ok, so you did do some research - that wasn't apparent from your posts, so I didn't know. Sorry about that.

[skalogryz]

I can't use FPProfiler for this for the following reason: it uses fcl-passrc to parse sources. I already tried using fcl-passrc to parse my sources, it can parse only 100 of 600 units........ yesss....

ok.. any commercial profilers?

btw, what it is in 500 units that passrc cannot handle them?

I know it won't help, but I need to say, that you're profiling in a wrong (non pascalish) manner

[hinst]

btw, what it is in 500 units that passrc cannot handle them?

things like this: {{}   (*{*)   //{
and some other things I can't recall now

[skalogryz]

things like this: {{}   (*{*)   //{
and some other things I can't recall now

This is odd. Parsing comments is straight forward for Pascal, since comments are not nested.

[Leledumbo]

things like this: {{}   (*{*)   //{
and some other things I can't recall now

This is odd. Parsing comments is straight forward for Pascal, since comments are not nested.

It is nestable in Delphi mode, but has to be of different type.

[skalogryz]

It is nestable in Delphi mode, but has to be of different type.

really? Embacradero made comments nestable?

Nestable comments put a serious  restriction on a developer

Code: [Select]

{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{
crzy comments like this one
}
would no longer be allowed.