Re: [fpc-pascal]RE: Debugging FPC

2003-08-21 Thread Peter Vreman
>> With compile modes: -gg -gl >> Aren't line info and tracebacks suppose to be shown, >> the above example does not show these. > > I think the problem comes with using exceptions. Normally, if a > run-time error occurs, the default exit proc will print the line > number info to stdout. But if an

[fpc-pascal]RE: Debugging FPC

2003-08-21 Thread Jeff Pohlmeyer
> With compile modes: -gg -gl > Aren't line info and tracebacks suppose to be shown, > the above example does not show these. I think the problem comes with using exceptions. Normally, if a run-time error occurs, the default exit proc will print the line number info to stdout. But if an exceptio

[fpc-pascal]Debugging FPC

2003-08-21 Thread James Mills
I think perhaps I need to repost my question as I saw the mailing list server go down yesterday... Hi, 1) Is there anyway of finding out the cooresponding source line when a program crashes and only outputs the following: An unhandled exception occurred at 0x080A33B1 : List index exceeds bounds

RE: [fpc-pascal]QWord vs. function Abs

2003-08-21 Thread Lubomir . Cabla
In a file \pp\source\rtl\inc\systemh.inc dated 26.10.2002 i found (only) these declarations about ABS function: Function abs(l:Longint):Longint; Function sqr(l:Longint):Longint; Function odd(l:Longint):Boolean; Function odd(l:Cardinal):Boolean; {$ifdef int64} Function odd(l:Int64):Boolean; Functio