On Fri, 11 May 2012 13:59:42 +0200 Sven Barth wrote:
> Am 11.05.2012 11:29, schrieb microcode
>> On Thu, 10 May 2012 17:14:45 + Mark Morgan Lloyd wrote:
>>
>>> You might find the fpc-devel mailing list interesting, although I think
>>> that everybody would admit that there is a shortage of doc
Am 11.05.2012 11:29, schrieb microc...@zoho.com:
On Thu, 10 May 2012 17:14:45 + Mark Morgan Lloyd wrote:
You might find the fpc-devel mailing list interesting, although I think
that everybody would admit that there is a shortage of documentation for
the entrails of the compiler.
Thanks, I
On Thu, 10 May 2012 17:14:45 + Mark Morgan Lloyd wrote:
> You might find the fpc-devel mailing list interesting, although I think
> that everybody would admit that there is a shortage of documentation for
> the entrails of the compiler.
Thanks, I'm subscribed but haven't seen any messages ye
Ludo Brands wrote:
- Maybe there's a workaround? IOW, can someone successfully
use massif
with FPC programs?
This is known problem not related to fpc. Run
valgrind --tool=massif --run-libc-freeres=no ./trivial_alloc
Fantastic, many thanks, it works like a charm now! :) Both on trivial
te
Sven Barth wrote:
You could try whether heaptrc is of any help for you (see here:
http://www.freepascal.org/docs-html/rtl/heaptrc/usage.html ). If not it
might at least provide a starting point if you should decide to write a
custom memory profiler. Otherwise I don't know of any FPC based memory
> Hi,
>
> I wanted to debug where my program uses the most memory.
> (There are no
> memory leaks, but I want to optimize memory usage on some
> large inputs.
> As the code is quite large, simply guessing which part is responsible
> becomes quite hard :) In the past, I happily used valgrind's
