Bug#490999: gcc-4.3 / qt3 misalignment

2008-12-08 Thread Julien Cristau
On Sun, 2008-12-07 at 20:16 +0100, Baurzhan Ismagulov wrote: > Now that #506713 is closed, I have a couple of questions regarding the > process: > > * The closing message mentions experimental; will the package be > available in lenny? If yes, will this happen automatically, or does > someone

Bug#490999: gcc-4.3 / qt3 misalignment

2008-12-07 Thread Baurzhan Ismagulov
On Mon, Nov 24, 2008 at 10:32:54AM +0100, Sune Vuorela wrote: > Ben Hutchins did some work on it and ended up filing a bug against gcc: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506713 > it got a much smaller testcase - and the gcc maintainer asks for additional > information that can eas

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-24 Thread Baurzhan Ismagulov
On Mon, Nov 24, 2008 at 10:32:54AM +0100, Sune Vuorela wrote: > Ben Hutchins did some work on it and ended up filing a bug against gcc: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506713 > it got a much smaller testcase - and the gcc maintainer asks for additional > information that can eas

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-24 Thread Sune Vuorela
On Monday 24 November 2008 10:29:46 Baurzhan Ismagulov wrote: > On Sun, Nov 23, 2008 at 09:59:19PM +0100, Sune Vuorela wrote: > > > Could it be > > > possible that qt3 overwrites memory somewhere? Wrong results for > > > t.hour() would also speak for that. > > > > I have read over and over the qdat

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-24 Thread Baurzhan Ismagulov
On Sun, Nov 23, 2008 at 09:59:19PM +0100, Sune Vuorela wrote: > > Could it be > > possible that qt3 overwrites memory somewhere? Wrong results for > > t.hour() would also speak for that. > > I have read over and over the qdatetime.cpp code, but I can't find anything > looking weird. Yes, so have

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-23 Thread Sune Vuorela
On Sunday 23 November 2008 21:46:35 Baurzhan Ismagulov wrote: > Could it be > possible that qt3 overwrites memory somewhere? Wrong results for > t.hour() would also speak for that. I have read over and over the qdatetime.cpp code, but I can't find anything looking weird. src/tools/qdatetime.cpp

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-23 Thread Baurzhan Ismagulov
Hello Sune, On Sun, Nov 23, 2008 at 03:25:32PM +0100, Sune Vuorela wrote: > This gives bus error on sparc ... > except in some cases where it segfaults. Thanks for the test case! This results in the following bt: #0 0xf7f38168 in _dl_fixup () from /lib/ld-linux.so.2 #1 0xf7f3ea34 in _dl_runtim

Bug#490999: gcc-4.3 / qt3 misalignment

2008-11-23 Thread Sune Vuorela
Hi! This gives bus error on sparc #include #include int main(int argc, char* argv[] ) { QTime t = QTime::currentTime().addSecs(0); int hour = t.hour(); std::cout << "hour" < signature.asc Description: This is a digitally signed message part.