On 26 Jun 2008, at 15:07, Bent Normann Olsen wrote:
Another option is -gh to turn on memory debugging, possibly also
adding
"keepreleased:=true" to your program initialisation code (but in that
case watch the memory usage, as no memory will really be released in
that case).
Now if I use the
On 23 Jun 2008, at 11:21, Joost van der Sluis wrote:
Op zaterdag 21-06-2008 om 19:23 uur [tijdzone -0700], schreef David
Emerson:
1. If the setlength function is creating an array of things which
happen
to be stored as pointers (ansistrings in str_arr or class instances
in
cls_arr) then wi
Thanks, Joost, for all of your answers! It looks like I need to write
*more* cleanup code, and double-check it all.
One question remains:
> After calling setlength, the items in the array are not initialised.
>
> [...]
>
> Initialising the strings you can do by setting them to an empty
> stri
Hi,
Thanks for the input.
> > Any clue or help is much appreciated.
>
> You could try compiling your program (and possibly the lcl) with -gttt
> to turn on filling local variables and out parameters with garbage,
> which may help in case the problem is an uninitialised value.
I did try -gttt, a
Hi
Any problem with this file? Gives me a runtime error 203. Its a code
compiled using ppcrossarm-2.3.1 with Gtk1.
debian:/home/kodi# readelf -h so/muraj1
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data:
On 26 Jun 2008, at 10:56, Bent Normann Olsen wrote:
I can't reproduce the crash on a test program, so I suspect it has
to do
with large applications with tons of strings.
It's most likely due to memory corruption in the large application
caused by a bug in it.
Could FPC have troubles h
On Wed, 25 Jun 2008 13:06:58 +0200 (CEST)
Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 25 Jun 2008, Peter Vreman wrote:
>
>[...]
> > The ppu unit from the compiler and ppudump has become too much
> > dependent on other units of the compiler that i don't think it is
> > recommend
Hi,
I've posted this issue on the Lazarus mailing list few weeks ago, and no
breakthroughs. On the other hand, I suspect this problem could as well have
to do with FPC handling strings.
I am using FPC v2.2.0 [2008/05/29] for i386 with Mac OS X v10.4.11. And this
problem doesn't appear on the Win3
