Debugging GPC (was: Problems with OBJECTs) - Gpc

14 Jun 1997


      According to Bernhard Tschirren:
...
The program below causes a Segment Violation (SIGSEGV) during compilation
using GPC-970510 for DJGPP 2.01.
[...]
Procedure TObj.DisposeIndex;
{$M START}
    Procedure DisposeEntry(Var Entry:PEntry);
{$M STOP}
        Begin
            If (Entry <> Nil) Then
[...]
Thanks for the precise bug report.  This makes it easier to debug GPC.
I don't know how long it took you to find that place, but GPC has a
debugging option `-dY' to dump the source to `stderr' during compilation.
Using this, you immediately see the location where GPC crashed.
The bug, however, seems to be somewhat harder ... working on it ...
Peter
Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer
peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201]
 maintainer GNU Pascal [970510] - http://home.pages.de/~gnu-pascal/ [970125]