| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: _FORTIFY_SOURCE by default? |
| Date: | 2012-09-18 02:50:27 |
| Message-ID: | 1347936627.7329.1.camel@vanquo.pezone.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2012-09-16 at 15:58 -0400, Tom Lane wrote:
> Maybe we're talking past each other. What I thought you meant was
> adding this #define unconditionally, without any awareness of what it
> might do on particular platforms. If you are thinking of adding it
> only on platforms where it is considered standard, I can live with
> that.
I had suggested to put it into src/include/port/linux.h
>
> Another point to consider here is that (at least on Red Hat) I believe
> this enables address-space randomization; which is something I very
> much do not want to happen in debug builds.
I doubt that a preprocessor symbol has anything to do with address-space
randomization. You are probably thinking of some other option that
comes in with the hardening/security flags.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-18 03:10:26 | Re: _FORTIFY_SOURCE by default? |
| Previous Message | Robert Haas | 2012-09-18 02:18:01 | Re: [COMMITTERS] pgsql: Fix bufmgr so CHECKPOINT_END_OF_RECOVERY behaves as a shutdown c |