Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-15 Thread Peter Vreman
>> > The point is that there is no stack trace with line numbers on the >> > (obviously correct) exception, in spite of the option -gl (even when >> > explicitly using SysUtils). >> >> The problem is that the framepointer register EBP is 0 in the >> sigcontext. >> We can't solve this. > > So, where

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-14 Thread Anton Tichawa
Marco van de Voort wrote: On Thu, Jul 14, 2005 at 10:27:01AM +0200, Peter Vreman wrote: Tom Verhoeff a ?crit : The point is that there is no stack trace with line numbers on the (obviously correct) exception, in spite of the option -gl (even when explicitly using SysUtils). The

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-14 Thread Marco van de Voort
> On Thu, Jul 14, 2005 at 10:27:01AM +0200, Peter Vreman wrote: > > > Tom Verhoeff a ?crit : > > > > > > The point is that there is no stack trace with line numbers on the > > > (obviously correct) exception, in spite of the option -gl (even when > > > explicitly using SysUtils). > > > > The probl

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-14 Thread Tom Verhoeff
On Thu, Jul 14, 2005 at 10:27:01AM +0200, Peter Vreman wrote: > > Tom Verhoeff a écrit : > > > > The point is that there is no stack trace with line numbers on the > > (obviously correct) exception, in spite of the option -gl (even when > > explicitly using SysUtils). > > The problem is that the f

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-14 Thread Peter Vreman
> On Thu, Jul 14, 2005 at 01:12:23AM +0200, Marcel Martin wrote: >> Tom Verhoeff a écrit : >> >begin >> > VMyClass := TMyClass.Create; >> > //VMyClass.FP := VMyClass.P; { with this assignment, it works } >> > VMyClass.FP; { this causes an Access Violation } >> >> Of course, at this point FP =

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-13 Thread Tom Verhoeff
On Thu, Jul 14, 2005 at 01:12:23AM +0200, Marcel Martin wrote: > Tom Verhoeff a écrit : > >begin > > VMyClass := TMyClass.Create; > > //VMyClass.FP := VMyClass.P; { with this assignment, it works } > > VMyClass.FP; { this causes an Access Violation } > > Of course, at this point FP = nil sinc

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-13 Thread Marcel Martin
Let it be. I just saw that, in fact, you told about the problem in the subject of the post :-) mm ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-13 Thread Marcel Martin
Tom Verhoeff a écrit : begin VMyClass := TMyClass.Create; //VMyClass.FP := VMyClass.P; { with this assignment, it works } VMyClass.FP; { this causes an Access Violation } Of course, at this point FP = nil since you didn't set it. mm ___ fpc-

[fpc-pascal] Calling unassigned procedure gives no stack trace with -gl

2005-07-13 Thread Tom Verhoeff
When the following program is compiled with option -gl -Mdelphi and executed, it results in An unhandled exception occurred at $ : EAccessViolation : Access violation without a stack trace or line numbers. How come? Is that a bug? (If so, I will submit it as such.) The