[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: abort() traceability
|
From: |
Eric Blake |
|
Subject: |
Re: abort() traceability |
|
Date: |
Mon, 15 Jun 2009 06:03:08 -0600 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Bruno Haible on 6/15/2009 2:08 AM:
> What do the others think? Should we possibly extend stdlib.in.h so that
> abort() becomes a macro that produces a detailed error message, similar to
> what assert() does?
Only if you name it something other than abort(), to make it obvious that
it will be printing a message in addition to aborting. Besides, it is
possible to catch SIGABRT in order to do special handling, such as the way
m4 prints a bug reporting address rather than dumping core, and that must
continue to work whether the program sticks with abort() (no additional
message) or uses your new proposed macro (a new message in addition to the
bug reporting address triggered by the SIGABRT).
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAko2OHwACgkQ84KuGfSFAYAfqgCfTr0IHU+S1RzH3L/9Cnu8O649
53kAoMx1RYopGMUr2gnNQ5ibm8cxRFpj
=zQXH
-----END PGP SIGNATURE-----