Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2000-11

Heap trace

3 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Gabor DEAK JAHN

Hello,

I have spurious errors when using the heap trace feature (the actual compiler switches I use are -ghlc and -Crtoi; compiler version 1.00). It worked quite well with a small program but as it became larger, I started to get an access violation error when I called an object method (the error messages refers to the starting 'begin' of the procedure). The object is properly initialized and as far as I can tell, there is no error in the program; without the heap trace it works flawlessly.

Are there any known problems with this feature?

Regards,

   Gabor DEAK JAHN

------------------------------------------------------------------- Gabor DEAK JAHN -- Budapest, Hungary.
WWW: <http://www.tramontana.co.hu/>www.tramontana.co.hu E-mail:

Peter Vreman
Show quoted text 6 lines
Hello, I have spurious errors when using the heap trace feature (the actual compiler switches I use are -ghlc and -Crtoi; compiler version 1.00). It worked quite well with a small program but as it became larger, I

started>

to get an access violation error when I called an object method (the

erro> r

Show quoted text 5 lines
messages refers to the starting 'begin' of the procedure). The object is properly initialized and as far as I can tell, there is no error in the program; without the heap trace it works flawlessly. Are there any known problems with this feature?

Please try first the latest release 1.0.2

Peter

Peter Vreman
Show quoted text 9 lines
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

meanti> me,

Show quoted text 29 lines
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.

Without the sourcecode i can't see/try anything. So if you can attach the sourcecode that has the problem i can take a look at it.