| Summary: | skrooge 1.2.0 crash on opening report | ||
|---|---|---|---|
| Product: | [Applications] skrooge | Reporter: | Jaak Ristioja <jaak> |
| Component: | general | Assignee: | Stephane MANKOWSKI <stephane> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | stephane |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | 25.1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | gdb full backtrace | ||
Git commit c8b3feba0ba070b7540ffa75d223200cf8987cfe by Stephane Mankowski. Committed on 23/01/2012 at 09:49. Pushed by smankowski into branch 'Feature'. Related: bug 1, bug 2, bug 0 M +1 -0 CHANGELOG M +13 -11 plugins/skrooge/skrooge_report/skgreportpluginwidget.cpp http://commits.kde.org/skrooge/c8b3feba0ba070b7540ffa75d223200cf8987cfe |
Created attachment 68098 [details] gdb full backtrace Version: unspecified (using KDE 4.7.4) OS: Linux I was getting a skrooge-1.2.0 crash in plugins/skrooge/skrooge_report/skgreportpluginwidget.cpp:1027 with the line QStringList line1 = table.at(0); Looking at the code, it seems that it is not checked beforehand whether table.isEmpty() or table.empty() or table.count(). gdb showed that table is empty. Reproducible: Sometimes Steps to Reproduce: I was able to reproduce this every time on the day I first upgraded to 1.2.0 from 1.1.1. Can't reproduce now. I can't remember exactly, but the crash happened when (1) I started Skrooge and opened my custom report, or (2) when I switched to my custom report when I had another something else open in Skrooge. Actual Results: Crash. Expected Results: The report should have been properly opened.