Re: [fpc-pascal] IDE problems and crosscompiling

2005-10-27 Thread John Coppens
On Thu, 27 Oct 2005 21:05:56 +0200 Vincent Snijders <[EMAIL PROTECTED]> wrote: > Maybe a bit outdated, but this information was gold about a year ago, > http://wiki.lazarus.freepascal.org/index.php/Cross_compiling_for_Win32_under_Linux > > Also the buildfaq.pdf is a good (and up to date) read, if

Re: [fpc-pascal] IDE problems and crosscompiling

2005-10-27 Thread Vincent Snijders
John Coppens wrote: Hi guys... I wish it were as simple as the docs say. On Linux, I type 'fp' and nothing happens - not even the first text appears on the screen, no CPU activity... Ctrl-C exits. I even tried to recompile the entire source code, ran the fp there, same (lack of) luck. I don't

[fpc-pascal] IDE problems and crosscompiling

2005-10-27 Thread John Coppens
Hi guys... I wish it were as simple as the docs say. On Linux, I type 'fp' and nothing happens - not even the first text appears on the screen, no CPU activity... Ctrl-C exits. I even tried to recompile the entire source code, ran the fp there, same (lack of) luck. I don't care much for the IDE

Re: [fpc-pascal] log memory usage at runtime

2005-10-27 Thread Marc Santhoff
Am Donnerstag, den 27.10.2005, 16:40 +0200 schrieb Peter Vreman: > At 16:35 27-10-2005, you wrote: > >Hi, > > > >can the memory manager of fpc be watched at runtime? > > > >I'd like to log allocation and release of memory chunks by a GUI program > >under suspicion of leaking memory. This seems to

Re: [fpc-pascal] log memory usage at runtime

2005-10-27 Thread Peter Vreman
At 16:35 27-10-2005, you wrote: Hi, can the memory manager of fpc be watched at runtime? I'd like to log allocation and release of memory chunks by a GUI program under suspicion of leaking memory. This seems to be a problem only under some unknown circumstances... At least the total mem at st

[fpc-pascal] log memory usage at runtime

2005-10-27 Thread Marc Santhoff
Hi, can the memory manager of fpc be watched at runtime? I'd like to log allocation and release of memory chunks by a GUI program under suspicion of leaking memory. This seems to be a problem only under some unknown circumstances... At least the total mem at start and end of on run should be lo