[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Enabling compiler warning flags
|
From: |
Paul Eggert |
|
Subject: |
Re: Enabling compiler warning flags |
|
Date: |
Thu, 20 Dec 2012 15:49:27 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 |
On 12/20/2012 01:32 PM, Jeffrey Walton wrote:
Posix asserts
are useless during development under a debugger because the eventually
lead to SIGTERM. A much better approach in practice is to SIGTRAP.
I didn't follow all that message, but this part doesn't appear
to be correct. In POSIX, when assert() fails it leads to SIGABRT.
More generally, I'd rather focus this mailing list's energy into
improving Autoconf rather than worrying too much about
philosophical considerations.
- Re: Enabling compiler warning flags, (continued)
Re: Enabling compiler warning flags, Mike Frysinger, 2012/12/18
Re: Enabling compiler warning flags, Bob Friesenhahn, 2012/12/18
Re: Enabling compiler warning flags, Jeffrey Walton, 2012/12/20
Re: Enabling compiler warning flags, Russ Allbery, 2012/12/20