On 07/22/2010 05:22 AM, Victor Duchovni wrote:
On Wed, Jul 21, 2010 at 11:16:04PM +0200, Bas Mevissen wrote:
Can you try what happens if you replace at
typedef struct LOCAL_STATE {
int level;/* nesting level, for logging */
DELIVER_ATTR msg_attr;/*
Bas,
why should that make a difference if it was already proven that
changing the optimization level of the compiler fixes the issue, and
that it is probably a special corner case of hardened gcc3.4? I
suppose it has to do with it's stack protecting techniques etc.
2010/7/22 Bas Mevissen
Kai Krakow:
Bas,
why should that make a difference if it was already proven that
changing the optimization level of the compiler fixes the issue, and
that it is probably a special corner case of hardened gcc3.4? I
suppose it has to do with it's stack protecting techniques etc.
That is
On Thu, Jul 22, 2010 at 08:21:48AM +0200, Bas Mevissen wrote:
The local(8) and virtual(8) servers are separately compiled
programs (the latter being a stripped down version of the former).
The header files in question are not used in the same compilation
unit, and so this suggestion is
2010/7/22 Wietse Venema wie...@porcupine.org:
The pass-by-value structure is part of a Postfix safety mechanism,
and therefore I am not inclined to change it to work around buggy
compiler features.
Wise decision... Stick with that. :-)
--
Regards,
Kai Krakow
http://hurikhan77.wordpress.com/
Mystery solved:
Adding -O2 to CFLAGS (an -Ox parameter was missing) solved the problem.
Seems to be an GCC issue. I don't know if postfix should compile and work fine
without this or with another optimizer level.
If someone wants to debug this further: The pointer to the problem is within
Kai Krakow:
Mystery solved:
Adding -O2 to CFLAGS (an -Ox parameter was missing) solved the problem.
Seems to be an GCC issue. I don't know if postfix should compile and work fine
without this or with another optimizer level.
It *should* work with all optimization levels. except for:
- Bugs
2010/7/21 Wietse Venema wie...@porcupine.org:
That would be a compiler bug, possibly compiler version dependent.
Yep, I'm sure it is. The postfix ebuild from gentoo contains some
evidence that hardened gcc 3.4 may be problematic. In case you are
interested, follow up bug report:
On 07/21/2010 10:23 PM, Kai Krakow wrote:
2010/7/21 Wietse Venema wie...@porcupine.org:
That would be a compiler bug, possibly compiler version dependent.
Yep, I'm sure it is. The postfix ebuild from gentoo contains some
evidence that hardened gcc 3.4 may be problematic. In case you are
Original-Nachricht
Datum: Wed, 21 Jul 2010 22:23:06 +0200
Von: Kai Krakow hurikhan77+post...@googlemail.com
An: Postfix users postfix-users@postfix.org
Betreff: Re: postfix/local segfaults
2010/7/21 Wietse Venema wie...@porcupine.org:
That would be a compiler bug
On Wed, Jul 21, 2010 at 11:16:04PM +0200, Bas Mevissen wrote:
Can you try what happens if you replace at
typedef struct LOCAL_STATE {
int level;/* nesting level, for logging */
DELIVER_ATTR msg_attr;/* message/recipient attributes */
DELIVER_REQUEST
Hello!
I've just upgraded a working setup from postfix 2.5.5 to 2.6.6 on a
Gentoo box. Since then, when postfix/local tries to do user name
expansion (as far as I learned from the backtrace), it segfaults:
8--
#0 0x11286469 in vstring_strcpy
12 matches
Mail list logo
