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, Debian
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
6 matches
Mail list logo
