Purefiler - An alternative profiler

[Rings]

works now,

i had used 'Compile/Run' only,
and not 'Create Executable'

that is why the tool was never triggered.

[Didelphodon]

Gosh, and I was already almost gettn' weird. Anyway, that's good news, indeed!

By the way, a new version is online:

• Some bugfixes,
• frontcolors for (green/red) helping with eye-detection of procedures (procedure/procedureend) and
• a fulltextsearch invokable with CTRL-F (next item is found with F3)

Fetch it now :roll:

[Didelphodon]

A new version is online. Solved an divide-by-zero issue and "sharpened" the birdsview a bit.

[Michael Vogel]

I loaded all new versions, tried a lot of things, but bigger projects (more than 10.000 code lines) just do a crash when they are executed after being compiled with the PureFiler

[Didelphodon]

A new version is online. I solved two major bugs, one with fully qualified Include-files and one with memory-leak which lead to a crash. Please try, if that solves your problem.

[Didelphodon]

Again, a new version is online. Solved a lot of minor issues. Build 84.

[Didelphodon]

Another issue found and solved - build 85 is online.

[Didelphodon]

A new build is online: Build 89.
Now x64 is supported and Purefiler should be a bit faster now when compiling.

EDIT: Made a replacement-error - Build 90 is the corrected version.

[Didelphodon]

New build (92) is online. Solved a few major- and minor-issues.

[Didelphodon]

New version (build 112) is online.

Changes:
*) Better timing
*) Profiling of all programming-components (if, select, while, repeat, for, foreach, ...)
*) Better usability of the GUI
*) Un-Checking of Calls

Have phun,

Didel.

[jassing]

Any chance you'd consider releasing the source so one could customize it?

The only change I want (right now) is to have a comment (say w/in the 1st 10 lines) that would tell the purefiler to process it or not.. something like:

;UsePureFiler=yes
or
;UsePureFiler=no

that way; during a "build all" of a project that has multiple targets, it would run w/o user interaction (no yes/no dialog)

Perhaps even a:

;UsePureFiler=ask

which could be the default...

[Ramihyn_]

I tried it on a 40k lines multithreaded application several times. It did hang up the app every single time, so i had to kill the process. The hanging up happened after heavy multithreaded processing with network was started.

The profiler showed the (incomplete?) traces, but didn't manage to load any of them without crashing. Even if the app survived just about 20 seconds before it crashed, the loading of the resulting profile trace is unbelievably slow. Took over 30 minutes to load and then the profiler just crashed when it attempted to display the results.

[Didelphodon]

Any chance you'd consider releasing the source so one could customize it?

Hm, I don't know why everyone is always horny for one's source-code
Often it's actually not so easy to release software as open sourcecode as there might be many things like includes or libraries involved which are not wanted to be available as public sourcecode. Even bad documented/commented code could be the reason. My reasons not to make that publicly available are a bit of both.

The only change I want (right now) is to have a comment (say w/in the 1st 10 lines) that would tell the purefiler to process it or not.. something like:

;UsePureFiler=yes
or
;UsePureFiler=no

that way; during a "build all" of a project that has multiple targets, it would run w/o user interaction (no yes/no dialog)

Perhaps even a:

;UsePureFiler=ask

which could be the default...

I will see what I can do for you.

@All: Anyone any more wishes? I'd really like to have a whole package done at once than doing many little patches.

Cheers,
Didel.

[Didelphodon]

I tried it on a 40k lines multithreaded application several times. It did hang up the app every single time, so i had to kill the process. The hanging up happened after heavy multithreaded processing with network was started.

The profiler showed the (incomplete?) traces, but didn't manage to load any of them without crashing. Even if the app survived just about 20 seconds before it crashed, the loading of the resulting profile trace is unbelievably slow. Took over 30 minutes to load and then the profiler just crashed when it attempted to display the results.

Indeed the loading can be very slow. In the dimensions of your software I guess we're not talking about 1000000 line-invocations anymore. I guess that the traces are more about Gigs of diskspace. Besides that I have the guess that it's actually the loading of the source-code which is implemented kinda poorly (shame on me). It initially wasn't my intention to have this Profiler for 40k lines (!!) of code. Hm, don't know how I can help you this way, though I want, but I guess you wouldn't want to give me your sourcecode or your traces (which have the source-code included).

Cheers,
Didel.

[blueznl]

Didel, wouldn't it make sense to have a 'Tron' and 'Troff' statement in the code, so the user could specify what part of the code to trace?