[fpc-devel] Runtime error 217

[Ludo Brands]

Just spent an hour debugging a runtime error 217. No information just
runtime error 217, compilation aborted under lazarus and with lazbuild.
Rebuild fpc with debug information and ran the "offending" compile command
from the command line (on solaris). FPC crashed with an unhandled exception
"disk full error" in TCFileStream.Read??? Lots of free space so no disk
full. Figured out that Errno2InOutRes translates a lot of errors to "disk
full error". Finally it took truss to find out that reading a particar ppu
caused an EIO. ZFS filesystem appears to be damaged.

Wouldn't it be helpfull to catch the exception in TCFileStream and print out
the original error and the filename involved? Then re-raise it and abort
compilation.

Ludo

[Thaddy]

Post by Ludo Brands
Just spent an hour debugging a runtime error 217. No information just
runtime error 217, compilation aborted under lazarus and with lazbuild.
Rebuild fpc with debug information and ran the "offending" compile command
from the command line (on solaris). FPC crashed with an unhandled exception
"disk full error" in TCFileStream.Read??? Lots of free space so no disk
full. Figured out that Errno2InOutRes translates a lot of errors to "disk
full error". Finally it took truss to find out that reading a particar ppu
caused an EIO. ZFS filesystem appears to be damaged.
Wouldn't it be helpfull to catch the exception in TCFileStream and print out
the original error and the filename involved? Then re-raise it and abort
compilation.
Ludo
_______________________________________________
http://lists.freepascal.org/mailman/listinfo/fpc-devel

1. Rights errors are not really fpc's strength, - you are supposed to
take care of that yourself - (much worse with lazarus, which supposes
god mode for convienience)
2. Your compile should not and most likely would not have caused a ZFS
disk damage.

[Ludo Brands]

Post by Thaddy
2. Your compile should not and most likely would not have
caused a ZFS
disk damage.

That is not what I was suggesting. The damaged file caused the EIO and the
217. Not the other way around.
I found some entries in /var/adm/messages that signal a ZFS problem a few
hours ago. Cause???

Ludo

[Florian Klämpfl]

Post by Ludo Brands
Just spent an hour debugging a runtime error 217. No information just
runtime error 217, compilation aborted under lazarus and with lazbuild.
Rebuild fpc with debug information and ran the "offending" compile command
from the command line (on solaris). FPC crashed with an unhandled exception
"disk full error" in TCFileStream.Read???

Where does it do so?

[Ludo Brands]

Post by Ludo Brands

Post by Ludo Brands
Just spent an hour debugging a runtime error 217. No

information just

Post by Ludo Brands
runtime error 217, compilation aborted under lazarus and with
lazbuild. Rebuild fpc with debug information and ran the

"offending"

Post by Ludo Brands
compile command from the command line (on solaris). FPC

crashed with

Post by Ludo Brands
an unhandled exception "disk full error" in TCFileStream.Read???

Where does it do so?

Unfortunately I haven't saved the backtrace and the volume has been restored
from backup. So, truss output gone and I can't reproduce the problem.
However, from memory

TCFileStream.Read
tppufile.reloadbuf
tppufile.readdata
????
tppumodule.load_interface
tppumodule.loadppu
tppumodule.load_usedunits

No guarantee ;)