[bt-devel] [ bibletime-Bugs-1646286 ] malloc/free crash when creating search indices

[SourceForge.net]

Bugs item #1646286, was opened at 2007-01-27 21:11
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1646286&group_id=954

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Frontend / Bookshelf
Group: in progress
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: David Ormand (dlormand)
Assigned to: Martin Gruner (mgruner)
Summary: malloc/free crash when creating search indices

Initial Comment:
Program starts fine.  Select "Settings", then "Bookshelf Manager", then "Manager Search Indices", select a Bible text, then "Create Selected Indices".

Sometimes the error is:
*** glibc detected *** malloc(): memory corruption (fast): 0x10547d78 ***
*** BibleTime got signal 6 (Crashing). Trying to save settings.
Alarm clock

Sometimes the error is:
*** glibc detected *** malloc(): memory corruption: 0x1049a8d0 ***
*** BibleTime got signal 6 (Crashing). Trying to save settings.
Alarm clock

(different pointer values every time, of course.)

Doesn't seem to matter if the user is root or not, or where the text modules are located (/usr/local/share/sword or ~/.sword).

malloc failures seem to associate with KJV and MKJV, and free failures seem to associate with RSV and ISV.

BibleTime version 1.6.2
Qt version 3.3.6
running KDE 3.5.4 on PowerMac G4 with 2.6.18.3 kernel.
Slackintosh 11 distro


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-02-10 09:02

Message:
Logged In: NO 

FYI

----------  Weitergeleitete Nachricht  ----------

Subject: Re: [ bibletime-Bugs-1646286 ] malloc/fr
Date: Samstag, 10. Februar 2007
From: "David Ormand" <dlormand at users.sourceforge.net>
To: mgruner at users.sourceforge.net


Message body follows:

>Can you please test if this also happens with 1.6.3? If so,
please provide
>more details (stack backtrace).

Yep, still does it.  That's 1.6.3b, right?

Can you advise how to generate a stack backtrace?  I figured
it would leave a core file somewheres, but I can't find it!
 I understand such data can be extracted from core files,
but I've never done it personally.

Also, is this the appropriate way to process a bug report
with you, or is there a more "official" method via sourceforge?


--
This message has been sent to you, a registered SourceForge.net user,
by another site user, through the SourceForge.net site.  This message
has been delivered to your SourceForge.net mail alias.  You may reply
to this message using the "Reply" feature of your email client, or
using the messaging facility of SourceForge.net at:
https://sourceforge.net/sendmessage.php?touser=1703490

-------------------------------------------------------

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2007-02-09 00:44

Message:
Logged In: YES 
user_id=169722
Originator: NO

Can you please test if this also happens with 1.6.3? If so, please provide
more details (stack backtrace).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1646286&group_id=954