Bug 120250 - crash on opening po file
Summary: crash on opening po file
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kbabel
Classification: Miscellaneous
Component: KBabelDict (show other bugs)
Version: 1.11
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Stanislav Visnovsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-16 16:38 UTC by Andras VOROSKOI
Modified: 2009-05-09 21:27 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
this is the po file that kills kbabel (99.61 KB, text/x-gettext-translation)
2006-01-16 16:40 UTC, Andras VOROSKOI
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andras VOROSKOI 2006-01-16 16:38:56 UTC
Version:           1.11 (using KDE KDE 3.5.0)
Installed from:    Unlisted Binary Package
Compiler:          gcc4 
OS:                Linux

Kbabel crashes when i open a po file. It works fine in most cases, but this file kills it always.

Here is that po file: http://frugalware.org/~voroskoi/hu.po

I've reported this problem for the first time in #117968, but Nicolas suggested to open a new bug.
Comment 1 Andras VOROSKOI 2006-01-16 16:40:30 UTC
Created attachment 14274 [details]
this is the po file that kills kbabel
Comment 2 Nicolas Goutte 2006-01-17 10:13:25 UTC
Thank you! For me the file loads correctly however. :-(
Comment 3 Robert Gomułka 2006-01-29 21:28:10 UTC
I can confirm the problem (Robert Gomulka).
My platform: Debian Gnu Linux/x86, KDE 3.5, KBabel 1.11.1
Unfortunately I have no packages with debug information, so core file gives no information:
Core was generated by `kbabel attachment.po'.
Program terminated with signal 11, Segmentation fault.
#0  0xb7f6b52f in ?? ()
(gdb) bt
#0  0xb7f6b52f in ?? ()
#1  0x00000012 in ?? ()
#2  0x00000000 in ?? ()
Comment 4 Andras VOROSKOI 2006-02-10 14:56:15 UTC
It seems to be fixed in 1.11.1 (KDE 3.5.1)
Comment 5 Robert Gomułka 2006-02-10 19:13:33 UTC
It is not fixed. I have 1.11.2 and it crashes. But only with my old kbabeldict. When I rename it (for example to kbabeldict.old), it stops crashing (~/.kde/share/apps/kbabeldict).
So please reassign this bug to db search engine.
Comment 6 Nicolas Goutte 2006-02-11 11:42:20 UTC
Thank you for debugging that it is a kdedict problem. 

Have you updated from a previous version, especially of a previous version of the Berkeley database library?

If yes, may be you want to try to save the database. See the threads where there are emails of Yury Tarasievich in the archives of the kbabel mailing list: http://mail.kde.org/pipermail/kbabel/2005-November/subject.html

Have a nice day!
Comment 7 Robert Gomułka 2006-02-11 16:25:30 UTC
Thank you for your information.
Actually I use KBabel for a long time - even years. I think in the meantime I survived many transitions, Berkeley DB could easily be one of them.
Because I have no idea what can I use those db files for, I will probably delete those old ones. However there should be some crash prevention in KBabel in case of detecting e.g. older db files, instead of just exiting due to SIG11.
Comment 8 Nicolas Goutte 2006-02-11 16:32:00 UTC
On Saturday 11 February 2006 16:25, Robert "GomuÅka" wrote:
(...)
> Thank you for your information.
> Actually I use KBabel for a long time - even years. I think in the meantime
> I survived many transitions, Berkeley DB could easily be one of them.
> Because I have no idea what can I use those db files for, I will probably
> delete those old ones. However there should be some crash prevention in
> KBabel in case of detecting e.g. older db files, instead of just exiting
> due to SIG11.


In case of old files, Berkeley returns an error asking to update the database, 
KBabel can do that if the user wants. The conversion itself is done by the 
Berkeley library. The problem is that that procedure succeeds and that the 
Berkeley library does not seem to detect that the database has a problem... 
until it is too late.

Have a nice day!
Comment 9 dr.t.vasudevan 2007-04-21 14:33:39 UTC
Bug #120250 (this bug), bug #121376 and bug #142009 seem to be mutual duplicates.
Comment 10 Nick Shaforostoff 2009-05-09 21:27:30 UTC
I couldn't crash Lokalize with this file.