Re[3]: [fpc-devel] protecting dataspace suggestion

2006-04-17 Thread Peter Vreman
At 13:44 17-4-2006, you wrote: > >I don't understand the way FPC stores debug information: line info etc. It > >seems useful to not lose this information or at least know, that it was > >overwritten. > >I got some run time errors with no line info (when compiled with -gcl > >option), all of them

Re[3]: [fpc-devel] protecting dataspace suggestion

2006-04-17 Thread Пётр Косаревский
> >I don't understand the way FPC stores debug information: line info etc. It > >seems useful to not lose this information or at least know, that it was > >overwritten. > >I got some run time errors with no line info (when compiled with -gcl > >option), all of them should be "unreproducible", be

Re: [fpc-devel] protecting dataspace suggestion

2006-04-17 Thread Peter Vreman
At 11:59 17-4-2006, you wrote: Sometimes RTL dataspace, including run time error numbers (may be some debug information), is corrupted because of poor programming. It's a reason for getting strange messages like "Run time error 998" (may be omitting line number information etc). FPC has imple

[fpc-devel] protecting dataspace suggestion

2006-04-17 Thread Пётр Косаревский
Sometimes RTL dataspace, including run time error numbers (may be some debug information), is corrupted because of poor programming. It's a reason for getting strange messages like "Run time error 998" (may be omitting line number information etc). FPC has implemented e.g. some checks for point