Re: IRC meeting 2011-05-25 (Wednesday!)

2011-05-24 Thread Oz
thanks this is the first reply i have gotten back. On Tue, May 24, 2011 at 11:07 AM, Richard Braun wrote: > On Sun, May 22, 2011 at 08:46:50PM -0500, Oz wrote: >> do you all ever hold meetings on saturdays? >> >> what day of the week are most of you off from work? > > Personally, when I'm not wo

Re: Introducing the hardening-wrapper package (was: Exim4 problems)

2011-05-24 Thread Svante Signell
On Mon, 2011-05-23 at 23:48 +0200, Samuel Thibault wrote: > #624696 - exim4: broken build with gcc-4.6 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624696 > > #624743 - gcc-4.6 -D_FORTIFY_SOURCE=2 miscompiles exim4 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624743 > > I'll follow-up

Re: IRC meeting 2011-05-25 (Wednesday!)

2011-05-24 Thread Richard Braun
On Sun, May 22, 2011 at 08:46:50PM -0500, Oz wrote: > do you all ever hold meetings on saturdays? > > what day of the week are most of you off from work? Personally, when I'm not working, I'm not on IRC either, nor reading mail. So saturdays or sundays would be problematic too. I guess it may be

Re: Mach bug trigger: Re: Updated gdb patch

2011-05-24 Thread Jérémie Koenig
On Wed, May 18, 2011 at 11:15 AM, Svante Signell wrote: > On Tue, 2011-05-17 at 17:34 +0200, Svante Signell wrote: >> (gdb) run --version >> (gdb) Starting program: /usr/sbin/exim4 --version >> >> This warning disappeared: >> warning: Error setting exception port for process 1701: (ipc/send) >> in

Re: Bug#624743: cannot reproduce

2011-05-24 Thread Samuel Thibault
Thomas Schwinge, le Tue 24 May 2011 11:32:40 +0200, a écrit : > On Mon, 23 May 2011 23:59:27 +0200, Samuel Thibault > wrote: > > [exim4 SEGFAULT with fortifying options] > > > It looks like gcc-4.6 is here erroneously optimizing > > __builtin___memmove_chk into a memcpy call! > > This is not a

Re: Bug#624743: cannot reproduce

2011-05-24 Thread Thomas Schwinge
Hallo! On Mon, 23 May 2011 23:59:27 +0200, Samuel Thibault wrote: > [exim4 SEGFAULT with fortifying options] > It looks like gcc-4.6 is here erroneously optimizing > __builtin___memmove_chk into a memcpy call! This is not a GCC bug (), but it is a glibc header bug (