At 11/20/2000 12:00, you wrote:
Dear Peter,
> I have spurious errors when using the heap trace feature (the actual Please try first the latest release 1.0.2
I doesn't seem to go away. I went on developing the program in the meantime, so the error message pops up in a different procedure right now.
I compiled to assembly and found the following code fragment:
.text
.balign 16
.stabs
"PEXTRACTFILEPATH:f30",36,0,94,_FONTS$$_PEXTRACTFILEPATH$PATHSTRING$PCHAR .Ll1:
.stabn 68,0,94,.Ll1 - _FONTS$$_PEXTRACTFILEPATH$PATHSTRING$PCHAR # [94] begin
_FONTS$$_PEXTRACTFILEPATH$PATHSTRING$PCHAR:
pushl %ebp
movl %esp,%ebp
subl $264,%esp
.Ll2:
.stabn 68,0,94,.Ll2 - _FONTS$$_PEXTRACTFILEPATH$PATHSTRING$PCHAR movl $0,-264(%ebp)
movl $0,-260(%ebp)
pushl $1
call FPC_PUSHEXCEPTADDR
pushl %eax <<<<<<<<<<<<<<<< access violation call FPC_SETJMP
pushl %eax
testl %eax,%eax
jne .L6
The parameters passed to the procedure are valid. As I said, it works without a glitch without the trace.
Regards,
Gabor DEAK JAHN
------------------------------------------------------------------- Gabor DEAK JAHN -- Budapest, Hungary.
WWW: <http://www.tramontana.co.hu/>www.tramontana.co.hu E-mail:
