Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2011-07

Runtime error 217

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

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

Reply by email

Thaddy
to Ludo Brands
Ludo Brands wrote 19 lines
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 _______________________________________________ fpc-devel maillist - 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.

Reply by email

Ludo Brands
to 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

Reply by email

Florian Klämpfl
to Ludo Brands: Just spent an hour debugging a runtime error 217. No information just runtime error 217,…
Ludo Brands wrote 5 lines
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?

Reply by email

Ludo Brands
to Florian Klämpfl
Show quoted text 11 lines
Am 04.07.2011 17:42, schrieb 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?

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 ;)

Reply by email