kbabel: crash with some .po file

Bug #12567 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
kdelibs (Debian)
Fix Released
Unknown
kdelibs (Ubuntu)
Invalid
High
Andreas Mueller

Bug Description

Automatically imported from Debian bug report #289646 http://bugs.debian.org/289646

Revision history for this message
In , Steve Langasek (vorlon) wrote :

tags 289646 experimental
thanks

Matias,

I am not able to reproduce this bug using the packages in sarge. Can you
please downgrade kdelibs4 on your system to the version in unstable, to
confirm whether this bug still exists for you?

Thanks,
--
Steve Langasek
postmodern programmer

Revision history for this message
In , Dato Simó (dato) wrote :

reassign 289646 kdelibs4
tags 289646 - experimental
tags 289646 + sid
thanks

* Matías Costa [Mon, 10 Jan 2005 11:33:09 +0100]:

Hi Matías,

> kbabel crashes (SIGSEGV) with certain entries. This makes imposible to work.
> You can find a file with this problem at

> http://webs.ono.com/uucp/knewsticker_crash.po

> Open the file, go to entry 98 (Crtl+g). Try to save or move to other entry.

  After some investigations, it seems that the crash is libkspell
  related. Can you tell us your settings under KControl -> KDE
  Components -> Spell checker? And to confirm that is really that: what
  happens if you chmod -x /usr/bin/[ai]spell?

* Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:

> I am not able to reproduce this bug using the packages in sarge. Can you
> please downgrade kdelibs4 on your system to the version in unstable, to
> confirm whether this bug still exists for you?

  Seems to me that the version of kdelibs4 in sarge is not affected. The
  bogus version has hit unstable, though. Reassigning and tagging
  accordingly.

  Thanks.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

You've come to the right place. At debian-devel we are always willing
to argue over the meanings of words.
                -- seen on debian-devel@l.d.o

Revision history for this message
In , Matias Costa (mcc3) wrote : Re: Bug#289646: kbabel: crash with some .po file

El Martes 18 Enero 2005 14:14, Steve Langasek escribió:
> tags 289646 experimental
> thanks
>
> Matias,
>
> I am not able to reproduce this bug using the packages in sarge. Can you
> please downgrade kdelibs4 on your system to the version in unstable, to
> confirm whether this bug still exists for you?

apt-get kdelibs4/unstable kdelibs-bin/unstable. The problem is still there.

> Thanks,

Revision history for this message
In , Matias Costa (mcc3) wrote :

El Miércoles 19 Enero 2005 01:08, Adeodato Simó escribió:
> reassign 289646 kdelibs4
> tags 289646 - experimental
> tags 289646 + sid
> thanks
>
> * Matías Costa [Mon, 10 Jan 2005 11:33:09 +0100]:
>
> Hi Matías,
>
> > kbabel crashes (SIGSEGV) with certain entries. This makes imposible to
> > work. You can find a file with this problem at
> >
> > http://webs.ono.com/uucp/knewsticker_crash.po
> >
> > Open the file, go to entry 98 (Crtl+g). Try to save or move to other
> > entry.
>
> After some investigations, it seems that the crash is libkspell
> related. Can you tell us your settings under KControl -> KDE
> Components -> Spell checker? And to confirm that is really that: what
> happens if you chmod -x /usr/bin/[ai]spell?

Nothing, the problems is still there. The same with ispell or aspell, with
utf-8 or iso-1889-15. But you are right, without automatic spell check kbabel
does not crash.

> * Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:
> > I am not able to reproduce this bug using the packages in sarge. Can you
> > please downgrade kdelibs4 on your system to the version in unstable, to
> > confirm whether this bug still exists for you?
>
> Seems to me that the version of kdelibs4 in sarge is not affected. The
> bogus version has hit unstable, though. Reassigning and tagging
> accordingly.
>
> Thanks.

Revision history for this message
In , Riku Voipio (riku-voipio) wrote :

On Wed, Jan 19, 2005 at 10:02:47AM +0100, Matías Costa wrote:
> > * Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:
> > > I am not able to reproduce this bug using the packages in sarge. Can you
> > > please downgrade kdelibs4 on your system to the version in unstable, to
> > > confirm whether this bug still exists for you?

> > Seems to me that the version of kdelibs4 in sarge is not affected. The
> > bogus version has hit unstable, though. Reassigning and tagging
> > accordingly.

Yesterday I was able to reproduce this on sarge, not today anymore.
however, on sarge I can get kbabel to crash by pressing "apply" in
"project properties/spellchecking" tab while the spell-as-you-go is
selected, which is probably the same bug.

#0 0x4138868f in mallopt () from /lib/tls/i686/cmov/libc.so.6
#1 0x41387ab3 in malloc () from /lib/tls/i686/cmov/libc.so.6
#2 0x412c32ee in operator new () from /usr/lib/libstdc++.so.5
#3 0x40f28a20 in QGArray::newData () from /usr/lib/libqt-mt.so.3
#4 0x40f279bb in QGArray::QGArray () from /usr/lib/libqt-mt.so.3
#5 0x40f1975c in QCString::QCString () from /usr/lib/libqt-mt.so.3
#6 0x40f1a710 in QCString::mid () from /usr/lib/libqt-mt.so.3
#7 0x40888a15 in KProcIO::readln () from /usr/lib/libkdecore.so.4
#8 0x40695f71 in KSpell::check2 () from /usr/lib/libkdeui.so.4
#9 0x40698c25 in KSpell::qt_invoke () from /usr/lib/libkdeui.so.4
#10 0x40c764a6 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x40888cca in KProcIO::readReady () from /usr/lib/libkdecore.so.4
#12 0x4088881a in KProcIO::controlledEmission () from/usr/lib/libkdecore.so.4
#13 0x408887bd in KProcIO::ackRead () from /usr/lib/libkdecore.so.4
#14 0x40695fd3 in KSpell::check2 () from /usr/lib/libkdeui.so.4

with the lines 8-13 repeated infinetly.

Revision history for this message
In , Frans Pop (aragorn) wrote :

I've also been having crashes using kbabel in Sarge (see #289646). I've
had crashes with several po files now.

The behavior is somewhat eratic: when I first had the crash, I could
always reproduce it, now I find that sometimes the crash does not happen.
Very likely my crashes are related to this BR.

The tag 'sid' for this bug is probably _not_ correct!

||/ Name Version
+++-=============================-=======
ii kbabel 3.3.1-2
ii kdelibs 3.3.1-4
ii kdelibs4 3.3.1-4

Revision history for this message
In , Dato Simó (dato) wrote :

tag 289646 - sid
thanks dude

> The tag 'sid' for this bug is probably _not_ correct!

  Yeah, I forgot to remove it after Riku's mail. In the future, please
  feel free to do control@ handling yourself when you're confident :-)
  (At least in KDE land.)

  Cheers (and congrats for your AM ;-),

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

The pure and simple truth is rarely pure and never simple.
                -- Oscar Wilde

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #289646 http://bugs.debian.org/289646

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (5.3 KiB)

Message-Id: <email address hidden>
Date: Mon, 10 Jan 2005 11:33:09 +0100
From: =?utf-8?q?Mat=C3=ADas_Costa?= <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kbabel: crash with some .po file

Package: kbabel
Version: 4:3.3.1-2
Severity: grave
Justification: renders package unusable

kbabel crashes (SIGSEGV) with certain entries. This makes imposible to work.
You can find a file with this problem at

http://webs.ono.com/uucp/knewsticker_crash.po

Open the file, go to entry 98 (Crtl+g). Try to save or move to other entry.
Backtrace:

(no debugging symbols found)
-- message repeats 23 times --
[Thread debugging using libthread_db enabled]
[New Thread -1222682240 (LWP 4546)]
(no debugging symbols found)
-- message repeats 22 times --
[KCrash handler]
#4 0xb66e0d45 in DataBaseManager::addLocation ()
   from /usr/lib/kde3/kbabeldict_dbsearchengine.so
#5 0xb66dec89 in DataBaseManager::putItem ()
   from /usr/lib/kde3/kbabeldict_dbsearchengine.so
#6 0xb66e169a in DataBaseManager::putNewTranslation ()
   from /usr/lib/kde3/kbabeldict_dbsearchengine.so
#7 0xb66d7e25 in KDBSearchEngine::stringChanged ()
   from /usr/lib/kde3/kbabeldict_dbsearchengine.so
#8 0x080ec354 in KBabelDictBox::prevResult ()
#9 0x08091df1 in QMemArray<char>::detach ()
#10 0x08087708 in KBabelView::update ()
#11 0x08086eed in KBabelView::update ()
#12 0x0808f8a0 in KBabelView::staticMetaObject ()
#13 0xb71db52c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb71db354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb7a0edbb in KAction::activated () from /usr/lib/libkdeui.so.4
#16 0xb7a0e78f in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#17 0xb7a0efc1 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#18 0xb71db52c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb71db354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb77f619b in KAccelPrivate::menuItemActivated ()
   from /usr/lib/libkdecore.so.4
#21 0xb77f49d8 in KAccelPrivate::eventFilter () from /usr/lib/libkdecore.so.4
#22 0xb71d8e5e in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#23 0xb71d8d8c in QObject::event () from /usr/lib/libqt-mt.so.3
#24 0xb721160f in QWidget::event () from /usr/lib/libqt-mt.so.3
#25 0xb72cfca2 in QMainWindow::event () from /usr/lib/libqt-mt.so.3
#26 0xb717ebcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb717e6c4 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7771e03 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb77f394b in KAccelEventHandler::x11Event ()
   from /usr/lib/libkdecore.so.4
#30 0xb7777dcf in KApplication::x11EventFilter ()
   from /usr/lib/libkdecore.so.4
#31 0xb71074a8 in qt_set_x11_event_filter () from /usr/lib/libqt-mt.so.3
#32 0xb711114b in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#33 0xb71281a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#34 0xb7190f28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#35 0xb7190dd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#36 0xb717ee21 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#37 0x0...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 18 Jan 2005 05:14:14 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: kbabel: crash with some .po file

--W/+CTqSGWdiRg+8j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

tags 289646 experimental
thanks

Matias,

I am not able to reproduce this bug using the packages in sarge. Can you
please downgrade kdelibs4 on your system to the version in unstable, to
confirm whether this bug still exists for you?

Thanks,
--=20
Steve Langasek
postmodern programmer

--W/+CTqSGWdiRg+8j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB7QujKN6ufymYLloRApE6AJ9nMZH83fGJDp8avTuiVyPMAmWGRwCgxUGJ
HaVFGwgXg0NLcUMM3+7H3vk=
=Xq7O
-----END PGP SIGNATURE-----

--W/+CTqSGWdiRg+8j--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 19 Jan 2005 01:08:12 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: =?iso-8859-1?Q?Mat=EDas?= Costa <email address hidden>,
 Steve Langasek <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: kbabel: crash with some .po file

reassign 289646 kdelibs4
tags 289646 - experimental
tags 289646 + sid
thanks

* Mat� Costa [Mon, 10 Jan 2005 11:33:09 +0100]:

Hi Mat�,

> kbabel crashes (SIGSEGV) with certain entries. This makes imposible to work.
> You can find a file with this problem at

> http://webs.ono.com/uucp/knewsticker_crash.po

> Open the file, go to entry 98 (Crtl+g). Try to save or move to other entry.

  After some investigations, it seems that the crash is libkspell
  related. Can you tell us your settings under KControl -> KDE
  Components -> Spell checker? And to confirm that is really that: what
  happens if you chmod -x /usr/bin/[ai]spell?

* Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:

> I am not able to reproduce this bug using the packages in sarge. Can you
> please downgrade kdelibs4 on your system to the version in unstable, to
> confirm whether this bug still exists for you?

  Seems to me that the version of kdelibs4 in sarge is not affected. The
  bogus version has hit unstable, though. Reassigning and tagging
  accordingly.

  Thanks.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

You've come to the right place. At debian-devel we are always willing
to argue over the meanings of words.
                -- seen on debian-devel@l.d.o

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 19 Jan 2005 09:59:06 +0100
From: =?iso-8859-15?q?Mat=EDas_Costa?= <email address hidden>
To: Steve Langasek <email address hidden>,
 <email address hidden>
Subject: Re: Bug#289646: kbabel: crash with some .po file

El Martes 18 Enero 2005 14:14, Steve Langasek escribi=F3:
> tags 289646 experimental
> thanks
>
> Matias,
>
> I am not able to reproduce this bug using the packages in sarge. Can you
> please downgrade kdelibs4 on your system to the version in unstable, to
> confirm whether this bug still exists for you?

apt-get kdelibs4/unstable kdelibs-bin/unstable. The problem is still there.

> Thanks,

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 19 Jan 2005 10:02:47 +0100
From: =?iso-8859-1?q?Mat=EDas_Costa?= <email address hidden>
To: <email address hidden>,
 Adeodato =?iso-8859-1?q?Sim=F3?= <email address hidden>
Subject: Re: kbabel: crash with some .po file

El Mi=E9rcoles 19 Enero 2005 01:08, Adeodato Sim=F3 escribi=F3:
> reassign 289646 kdelibs4
> tags 289646 - experimental
> tags 289646 + sid
> thanks
>
> * Mat=EDas Costa [Mon, 10 Jan 2005 11:33:09 +0100]:
>
> Hi Mat=EDas,
>
> > kbabel crashes (SIGSEGV) with certain entries. This makes imposible to
> > work. You can find a file with this problem at
> >
> > http://webs.ono.com/uucp/knewsticker_crash.po
> >
> > Open the file, go to entry 98 (Crtl+g). Try to save or move to other
> > entry.
>
> After some investigations, it seems that the crash is libkspell
> related. Can you tell us your settings under KControl -> KDE
> Components -> Spell checker? And to confirm that is really that: what
> happens if you chmod -x /usr/bin/[ai]spell?

Nothing, the problems is still there. The same with ispell or aspell, with=
=20
utf-8 or iso-1889-15. But you are right, without automatic spell check kbab=
el=20
does not crash.

> * Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:
> > I am not able to reproduce this bug using the packages in sarge. Can y=
ou
> > please downgrade kdelibs4 on your system to the version in unstable, to
> > confirm whether this bug still exists for you?
>
> Seems to me that the version of kdelibs4 in sarge is not affected. The
> bogus version has hit unstable, though. Reassigning and tagging
> accordingly.
>
> Thanks.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 20 Jan 2005 11:55:34 +0200
From: Riku Voipio <email address hidden>
To: <email address hidden>
Subject: Re: Bug#289646: kbabel: crash with some .po file

On Wed, Jan 19, 2005 at 10:02:47AM +0100, Mat=EDas Costa wrote:
> > * Steve Langasek [Tue, 18 Jan 2005 05:14:14 -0800]:
> > > I am not able to reproduce this bug using the packages in sarge. C=
an you
> > > please downgrade kdelibs4 on your system to the version in unstable=
, to
> > > confirm whether this bug still exists for you?

> > Seems to me that the version of kdelibs4 in sarge is not affected. =
The
> > bogus version has hit unstable, though. Reassigning and tagging
> > accordingly.

Yesterday I was able to reproduce this on sarge, not today anymore.
however, on sarge I can get kbabel to crash by pressing "apply" in
"project properties/spellchecking" tab while the spell-as-you-go is
selected, which is probably the same bug.=20

#0 0x4138868f in mallopt () from /lib/tls/i686/cmov/libc.so.6
#1 0x41387ab3 in malloc () from /lib/tls/i686/cmov/libc.so.6
#2 0x412c32ee in operator new () from /usr/lib/libstdc++.so.5
#3 0x40f28a20 in QGArray::newData () from /usr/lib/libqt-mt.so.3
#4 0x40f279bb in QGArray::QGArray () from /usr/lib/libqt-mt.so.3
#5 0x40f1975c in QCString::QCString () from /usr/lib/libqt-mt.so.3
#6 0x40f1a710 in QCString::mid () from /usr/lib/libqt-mt.so.3
#7 0x40888a15 in KProcIO::readln () from /usr/lib/libkdecore.so.4
#8 0x40695f71 in KSpell::check2 () from /usr/lib/libkdeui.so.4
#9 0x40698c25 in KSpell::qt_invoke () from /usr/lib/libkdeui.so.4
#10 0x40c764a6 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x40888cca in KProcIO::readReady () from /usr/lib/libkdecore.so.4
#12 0x4088881a in KProcIO::controlledEmission () from/usr/lib/libkdecore.=
so.4
#13 0x408887bd in KProcIO::ackRead () from /usr/lib/libkdecore.so.4
#14 0x40695fd3 in KSpell::check2 () from /usr/lib/libkdeui.so.4

with the lines 8-13 repeated infinetly.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sun, 23 Jan 2005 16:22:33 +0100
From: Frans Pop <email address hidden>
To: <email address hidden>
Subject: kbabel: crash with some .po file

I've also been having crashes using kbabel in Sarge (see #289646). I've
had crashes with several po files now.

The behavior is somewhat eratic: when I first had the crash, I could
always reproduce it, now I find that sometimes the crash does not happen.
Very likely my crashes are related to this BR.

The tag 'sid' for this bug is probably _not_ correct!

||/ Name Version
+++-=============================-=======
ii kbabel 3.3.1-2
ii kdelibs 3.3.1-4
ii kdelibs4 3.3.1-4

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 23 Jan 2005 17:09:52 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Frans Pop <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#289646: kbabel: crash with some .po file

tag 289646 - sid
thanks dude

> The tag 'sid' for this bug is probably _not_ correct!

  Yeah, I forgot to remove it after Riku's mail. In the future, please
  feel free to do control@ handling yourself when you're confident :-)
  (At least in KDE land.)

  Cheers (and congrats for your AM ;-),

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

The pure and simple truth is rarely pure and never simple.
                -- Oscar Wilde

Revision history for this message
Andreas Mueller (amu) wrote :

tested with hoary, everything works fine.

test: downloaded http://webs.ono.com/uucp/knewsticker_crash.po
Opened the file, entry 98. Saved file and move to other entry.

Revision history for this message
In , Steinar H. Gunderson (sesse) wrote :

On Sun, Jan 23, 2005 at 04:22:33PM +0100, Frans Pop wrote:
> I've also been having crashes using kbabel in Sarge (see #289646). I've
> had crashes with several po files now.

I don't know if this helps you guys, but valgrind reports

==14218== Address 0x3588476C is 20 bytes inside a block of size 176 free'd
==14218== at 0x3414ACFA: operator delete(void*) (vg_replace_malloc.c:156)
==14218== by 0x347D7D32: KSpell::~KSpell() (in /usr/lib/libkdeui.so.4.2.0)
==14218== by 0x34DBFDFB: QObject::event(QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D65BFE: QApplication::internalNotify(QObject*, QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D651FD: QApplication::notify(QObject*, QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x348FFE02: KApplication::notify(QObject*, QEvent*) (in /usr/lib/libkdecore.so.4.2.0)
==14218== by 0x34D669F5: QApplication::sendPostedEvents(QObject*, int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D66875: QApplication::sendPostedEvents() (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D0F13C: QEventLoop::processEvents(unsigned) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D77FFE: QEventLoop::processEvents(unsigned, int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D65D6D: QApplication::processEvents(int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x8119459: (within /usr/bin/kbabel)
==14218== by 0x80FB1AB: (within /usr/bin/kbabel)
==14218== by 0x8100F3B: (within /usr/bin/kbabel)
==14218== by 0x807B8FA: (within /usr/bin/kbabel)

I'm unable to get a better stack trace as I don't have -dbg versions of
kdelibs4, and I'm unable to build them (see the other RC bug on kdelibs :-)).

/* Steinar */
--
Homepage: http://www.sesse.net/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 9 Feb 2005 01:17:52 +0100
From: "Steinar H. Gunderson" <email address hidden>
To: <email address hidden>
Subject: Re: kbabel: crash with some .po file

On Sun, Jan 23, 2005 at 04:22:33PM +0100, Frans Pop wrote:
> I've also been having crashes using kbabel in Sarge (see #289646). I've
> had crashes with several po files now.

I don't know if this helps you guys, but valgrind reports

==14218== Address 0x3588476C is 20 bytes inside a block of size 176 free'd
==14218== at 0x3414ACFA: operator delete(void*) (vg_replace_malloc.c:156)
==14218== by 0x347D7D32: KSpell::~KSpell() (in /usr/lib/libkdeui.so.4.2.0)
==14218== by 0x34DBFDFB: QObject::event(QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D65BFE: QApplication::internalNotify(QObject*, QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D651FD: QApplication::notify(QObject*, QEvent*) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x348FFE02: KApplication::notify(QObject*, QEvent*) (in /usr/lib/libkdecore.so.4.2.0)
==14218== by 0x34D669F5: QApplication::sendPostedEvents(QObject*, int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D66875: QApplication::sendPostedEvents() (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D0F13C: QEventLoop::processEvents(unsigned) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D77FFE: QEventLoop::processEvents(unsigned, int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x34D65D6D: QApplication::processEvents(int) (in /usr/lib/libqt-mt.so.3.3.3)
==14218== by 0x8119459: (within /usr/bin/kbabel)
==14218== by 0x80FB1AB: (within /usr/bin/kbabel)
==14218== by 0x8100F3B: (within /usr/bin/kbabel)
==14218== by 0x807B8FA: (within /usr/bin/kbabel)

I'm unable to get a better stack trace as I don't have -dbg versions of
kdelibs4, and I'm unable to build them (see the other RC bug on kdelibs :-)).

/* Steinar */
--
Homepage: http://www.sesse.net/

Revision history for this message
In , Pierre Habouzit (madcoder) wrote : Status update

I was able to reproduce the bug systematically even with kdelibs 3.3.2

  but with kbable running on top or experimental kdelibs 3.4.0~rc1, the
problem has gone.
--
·O· Pierre Habouzit
··O
OOO http://www.madism.org

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 3 Mar 2005 16:00:53 +0100
From: Pierre Habouzit <email address hidden>
To: <email address hidden>
Subject: Status update

I was able to reproduce the bug systematically even with kdelibs 3.3.2

  but with kbable running on top or experimental kdelibs 3.4.0~rc1, the
problem has gone.
--=20
=B7O=B7 Pierre Habouzit
=B7=B7O
OOO http://www.madism.org

Revision history for this message
In , Dato Simó (dato) wrote : On-the-Fly spell checking causing kbabel to crash

Hello Stanislav,

  we received in Debian a bug report claiming that KBabel crashed with a
  certain .po file, and that it seemed to be related to on-the-fly spell
  checking. You can read the full discussion at [1].

    [1] http://bugs.debian.org/289646

  The crash is reproducible for me when going to the entry #98 in the
  file mentioned in the report, being the spell checker language
  English. I suspect the crash is triggered because that entry is a
  little long, and as the checker language doesn't match the entry
  language (English vs. Spanish), a lot of misspelling signals are
  emitted.

  I've been having a look this afternoon, and after a lot of struggling
  I came to realice that using checkWord() instead of check() seems to
  improve things. There is this comment in kbabel/kbhighlighting.cpp:

  // yes I tried checkWord, the docs lie and it didn't give useful signals :-(

  However, is more than 2 years old, and checkWord() seems to do fine
  here. Perhaps you could considering making the change?

  Also, it may be that kdelibs is at fault, too (as per the backtrace).
  Sadly, I lack the knowledge to determine that, and anyway it seems
  that applications should really use the proper function that the API
  provides (checkWord, in this case).

  Thanks for considering,

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
    Listening to: Pet Shop Boys - You only tell me you love me when you're drunk

You cannot achieve the impossible without attempting the absurd.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 13 Mar 2005 21:07:27 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: Stanislav Visnovsky <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: On-the-Fly spell checking causing kbabel to crash

Hello Stanislav,

  we received in Debian a bug report claiming that KBabel crashed with a
  certain .po file, and that it seemed to be related to on-the-fly spell
  checking. You can read the full discussion at [1].

    [1] http://bugs.debian.org/289646

  The crash is reproducible for me when going to the entry #98 in the
  file mentioned in the report, being the spell checker language
  English. I suspect the crash is triggered because that entry is a
  little long, and as the checker language doesn't match the entry
  language (English vs. Spanish), a lot of misspelling signals are
  emitted.

  I've been having a look this afternoon, and after a lot of struggling
  I came to realice that using checkWord() instead of check() seems to
  improve things. There is this comment in kbabel/kbhighlighting.cpp:

  // yes I tried checkWord, the docs lie and it didn't give useful signals :-(

  However, is more than 2 years old, and checkWord() seems to do fine
  here. Perhaps you could considering making the change?

  Also, it may be that kdelibs is at fault, too (as per the backtrace).
  Sadly, I lack the knowledge to determine that, and anyway it seems
  that applications should really use the proper function that the API
  provides (checkWord, in this case).

  Thanks for considering,

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
    Listening to: Pet Shop Boys - You only tell me you love me when you're drunk

You cannot achieve the impossible without attempting the absurd.

Revision history for this message
In , Ben Burton (bab) wrote : kbabel patched

severity 289646 important
thanks mate

Hi. I've uploaded a new kdesdk with the s/check/checkWord/ patch, so
I'm lowering the severity of this bug. I'm leaving it open however,
since kbabel was in fact using the kdelibs API as documented -- in
theory kbabel was doing nothing wrong, so the problem would seem to be
in kdelibs (and thus still unfixed at the root of the problem).

Ben.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 25 Mar 2005 13:45:55 +1100
From: Ben Burton <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: kbabel patched

severity 289646 important
thanks mate

Hi. I've uploaded a new kdesdk with the s/check/checkWord/ patch, so
I'm lowering the severity of this bug. I'm leaving it open however,
since kbabel was in fact using the kdelibs API as documented -- in
theory kbabel was doing nothing wrong, so the problem would seem to be
in kdelibs (and thus still unfixed at the root of the problem).

Ben.

Revision history for this message
In , Christopher Martin (chrsmrtn-debian) wrote :

Since kbabel is fixed, and no other apps have reported the issue in a
year, I'm closing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.