FS#63239 - [kmymoney] Segmentation fault when inserting transaction
Attached to Project:
Community Packages
Opened by Henrique (hdante) - Saturday, 20 July 2019, 18:59 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Monday, 30 September 2019, 17:33 GMT
Opened by Henrique (hdante) - Saturday, 20 July 2019, 18:59 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Monday, 30 September 2019, 17:33 GMT
|
Details
Description:
When adding a certain investment transaction, kmymoney crashes with segmentation fault. Additional info: * package version(s) kmymoney 5.0.4-1 qt5-base 5.13.0-7 kcoreaddons 5.60.0-1 * config and/or log files etc. ==29496== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==29496== Access not within mapped region at address 0x0 ==29496== at 0x4B27137: InstitutionsModel::slotObjectModified(eMyMoney::File::Object, QString const&) (in /usr/lib/libkmm_models.so.5.0.4) ==29496== by 0x6992B6F: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/libQt5Core.so.5.13.0) ==29496== by 0x4C494A6: MyMoneyFile::objectModified(eMyMoney::File::Object, QString const&) (in /usr/lib/libkmm_mymoney.so.5.0.4) ==29496== by 0x4C574BC: MyMoneyFile::commitTransaction() (in /usr/lib/libkmm_mymoney.so.5.0.4) ==29496== by 0x4C5769E: MyMoneyFileTransaction::commit() (in /usr/lib/libkmm_mymoney.so.5.0.4) ==29496== by 0x39C7AE: ??? (in /usr/bin/kmymoney) ==29496== by 0x20DDCF: ??? (in /usr/bin/kmymoney) ==29496== by 0x6992B6F: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/libQt5Core.so.5.13.0) ==29496== by 0x5708E92: QAction::triggered(bool) (in /usr/lib/libQt5Widgets.so.5.13.0) ==29496== by 0x570B623: QAction::activate(QAction::ActionEvent) (in /usr/lib/libQt5Widgets.so.5.13.0) ==29496== by 0x5809C2C: ??? (in /usr/lib/libQt5Widgets.so.5.13.0) ==29496== by 0x5809E55: QAbstractButton::mouseReleaseEvent(QMouseEvent*) (in /usr/lib/libQt5Widgets.so.5.13.0) ==29496== If you believe this happened as a result of a stack ==29496== overflow in your program's main thread (unlikely but ==29496== possible), you can try to increase the size of the ==29496== main thread stack using the --main-stacksize= flag. ==29496== The main thread stack size used in this run was 8388608. * link to upstream bug report, if any Steps to reproduce: Operation specific. |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Monday, 30 September 2019, 17:33 GMT
Reason for closing: Upstream
Additional comments about closing: Not something I intend of trying to fix. Maybe the latest version does not suffer from this anymore.
Monday, 30 September 2019, 17:33 GMT
Reason for closing: Upstream
Additional comments about closing: Not something I intend of trying to fix. Maybe the latest version does not suffer from this anymore.
Comment by Henrique (hdante) -
Saturday, 20 July 2019, 19:25 GMT
Comment by Antonio Rojas (arojas) -
Sunday, 21 July 2019, 13:37 GMT
Confirmed segmentation fault also in kmymoney 5.0.5 compiled from
source.
Please report this upstream then