[fpc-pascal]Debugging FPC

James Mills prologic at daisy.ods.org
Fri Aug 22 09:23:39 CEST 2003


On Fri, Aug 22, 2003 at 11:08:14AM +1000, James Mills wrote:
> 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 (-1)
>   0x080A33B1

Also anyone out there, I'd really like to know if the above is possible
... I have to find the source of this particular defect in 19,000 LOC.
All it tells me is an index out of bounds, which could mean a number of
things.

Thanks in advance

James

> 
> 2) With compile modes: -gg -gl
>    Aren't line info and tracebacks suppose to be shown, the above
> example does not show these.
> 
> cheers
> James
> 
> -- 
> -
> -Zero Defect Software Engineers Group - ZDSEG
> -
> -You need only two tools. WD-40 and duct tape.
> -If it doesn't move and it should, use WD-40.
> -If it moves and shouldn't, use the tape.
> 
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal

-- 
-
-Zero Defect Software Engineers Group - ZDSEG
-
-You need only two tools. WD-40 and duct tape.
-If it doesn't move and it should, use WD-40.
-If it moves and shouldn't, use the tape.




More information about the fpc-pascal mailing list