[fpc-pascal]General error trapping
md at realmwireless.com
Wed Dec 20 08:08:32 CET 2000
Error trapping with Try..Except is the best way for error trapping.
I have questioned the actual utility of the signal handlers.
I would also question the understanding which signals are actually used
and the exact conditions that must exist for each signal to get executed
and the ramification of a given signal tripping.
Some signals cause core dumps, some don't. There does not seem to be a
good way to
of processing both before and after a core dump.
In fact, signals in general are a poor and loosely understood method of
external program signaling.
(short of pouring through the source code of course)
They seem to be a loose holdover from the past with no ability for
extensibility or customization without
significant kernel changes.
This is just a general observation.
Michael.VanCanneyt at wisa.be wrote:
> On Tue, 19 Dec 2000 BigMatt19 at aol.com wrote:
> > Hello all,
> > I am not totally familiar with how to go about error trapping in a Linux
> > envrironment. Right now I am trying to trap a "broken pipe" error. I am
> > assuming that this error would be written to linuxerror, but what directive
> > do I put a + sign to that will stop the program from crashing? Also, if
> > there is a general tutorial online about this sort of thing it would be
> > really cool if I could check that out.
> There is no general tutorial; the broken pipe error is a signal as far as I
> know (SIG_PIPE) . You must install a signal handler for this if you want to
> catch it.
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
More information about the fpc-pascal