[fpc-pascal]Debugging FPC

[James Mills]

On Fri, Aug 22, 2003 at 09:30:49AM +0200, jonas at freepascal.org wrote:
> 
> 
> On Fri, 22 Aug 2003, James Mills wrote:
> 
> > > 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.
> 
> Load the program in gdbpas. Put a breakpoint on HandleErrorFrame (with the

what is gdbpas ? I'm using FPC 1.0.6 ...

cheers
James

> command "b HANDLEERRORFRAME", caps are important). You can set command
> line parameters using "set args para1 para2 ...". If not all of the
> sources are in one directory, you can add directories that gdbpas has to
> search sources in using "directory dir1;dir2;dir3;...".
> 
> Next, type "run". When the breakpoint is hit, type "bt" (backtrace).
> 
> 
> Jonas
> 
> 
> _______________________________________________
> 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.