[fpc-pascal] Fingerprinting operation of a program

Mark Morgan Lloyd markMLl.fpc-pascal at telemetry.co.uk
Sun Feb 20 17:17:28 CET 2011


Darius Blaszyk wrote:
> On Feb 19, 2011, at 3:18 PM, Mark Morgan Lloyd wrote:
> 
>> Henry Vermaak wrote:
>>> On 18 February 2011 18:19, Mark Morgan Lloyd
>>> <markMLl.fpc-pascal at telemetry.co.uk> wrote:
>>>> I need to trace through a program, running on two different systems which
>>>> might or might not have the same OS, in order to find out where it's
>>>> failing.
>>>>
>>>> Before I start giving myself a gdb refresher course or manually inserting
>>>> trace messages, is there any way that I can extract a trace of procedure
>>>> entry/exits, preferably identified by name rather than by address, using
>>>> e.g. profiling hooks?
>>> Valgrind is probably what you need.  It doesn't work on windows, but
>>> people use it with wine.
>> Thanks Henry and Sven. I suspect that both FPP and Valgrind will end up being a substantial amount of work for a one-off problem... FPP in particular since it requires Lazarus to build but I'm trying to debug part of the Lazarus build process (bug 0018600).
>>
>> I'm about to start inserting debug messages. I might be some time.
>>
> FPP does not require Lazarus to build. It does have a Lazarus frontend though.

"Currently building the tools from commandline is broken. To build them 
you should use Lazarus. Start by opening the lazarus project files:"

http://wiki.freepascal.org/FPProfiler

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]



More information about the fpc-pascal mailing list