On Mon, Jan 12, 2009 at 04:48:04AM +, Debian Bug Tracking System wrote:
> BinNMU of qt-x11-free has been scheduled on sparc, which should correct this
> problem for testing and unstable as soon as the binary is uploaded.
Thank you!
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.
age is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
490999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin M
>> * When a newer compiler package is available for a distribution, is
>> everything rebuilt with it?
>>
>No.
But this is definitely non-sense. IIRC potentially every library is a
subject to be affected by the compiler's bug. The fact that other libs
don't cause such a destructive behavior (as
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
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
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
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
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
This is due to a compiler bug. The first two instructions of the
function QTime::addMSecs(int) are:
0xf7ce212c <_ZNK5QTime8addMSecsEi+0>: save %sp, -112, %sp
0xf7ce2130 <_ZNK5QTime8addMSecsEi+4>: ld [ %sp + 0x40 ], %i5
The second instruction is supposed to load the address where the
return
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
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
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.
tags 490999 +help
thanks
Hello All:
I've been looking into the code. This is the relevant(crashing) part:
kicker/applets/clock/clock.cpp:310
void DigitalClock::updateClock()
{
static bool colon = true;
QString newStr;
QTime t(_applet->clockGetTime());
int h = t.hour();
Processing commands for [EMAIL PROTECTED]:
> tags 490999 + confirmed
Bug#490999: kicker: crashes on startup
There were no tags set.
Tags added: confirmed
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
tags 490999 + confirmed
thanks
Hi,
gdb backtrace is attached.
Cheers,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
(sid)[EMAIL PROTECTED]:~$ gdb --args kicker --nofork
GNU gdb 6.8-debian
Copyri
Hello,
antradienis 04 Lapkritis 2008, Max Dmitrichenko rašė:
> addresses. GDB's backtrace is attached.
Is it? I don't see an attachment.
> What's next? Is there a way to build only kicker from sources?
I'm afraid there is no supported way to do this. You can try the following
though. Run ./confi
2008/11/5, Modestas Vainius <[EMAIL PROTECTED]>:
> Hello,
>
> antradienis 04 Lapkritis 2008, Max Dmitrichenko rašė:
>> addresses. GDB's backtrace is attached.
> Is it? I don't see an attachment.
Oops... Another try :)
>> What's next? Is there a way to build only kicker from sources?
> I'm afraid
Thanks Modestas!
Running kicker --nofork under gdb produces the same crash with SIGBUS.
Tested several times - backtrace doesn't differ except for object
addresses. GDB's backtrace is attached.
What's next? Is there a way to build only kicker from sources? Not
necessary to build a package. Rebuil
Hello,
antradienis 04 Lapkritis 2008, Max Dmitrichenko rašė:
> I would gladly help to debug this. But I'm very unfamiliar with KDE.
> Running kicker under gdb is meanless because every time it finishes
> successfuly, but kicker dies somewhere "outside" of gdb.
Try kicker --nofork
--
Modestas Vai
19 matches
Mail list logo
