On 19 jun 2007, at 10:50, Felipe Monteiro de Carvalho wrote:
I just suposed that on the backtrace gdb would show exactly where the
exception occured. There were more functions called at the point where
the exception really happens ... I don't know why he skiped some.
Debuging with the IDE step-
On 6/19/07, Jonas Maebe <[EMAIL PROTECTED]> wrote:
Without compilable example code, that is impossible to say.
Sorry for the noise, I found the problem =)
Inside the DrawTo function code there is a cast to an interface which
isn't implemented.
I just suposed that on the backtrace gdb would sh
On 18 jun 2007, at 22:06, Felipe Monteiro de Carvalho wrote:
Breakpoint 1, 0xe0a6 in fpc_raiseexception ()
(gdb) bt
#0 0xe0a6 in fpc_raiseexception ()
#1 0x00056682 in SYSUTILS_RUNERRORTOEXCEPT$LONGINT$POINTER$POINTER ()
#2 0x00010fd7 in SYSTEM_HANDLEERRORADDRFRAME$LONGINT$POINTER
$
