On 4 October 2017 at 02:58, Gaetan Bisson <[email protected]> wrote: > [2017-10-04 02:42:58 +0300] Lubomir I. Ivanov: >> Gaetan, can you please try applying the attached patch on the latest >> master for reference? > > Sure. With that patch I get a segfault: > > Thread 1 "subsurface" received signal SIGSEGV, Segmentation fault. > 0x00005555557ab79d in DiveTripModel::columnWidth(int) () > (gdb) bt > #0 0x00005555557ab79d in DiveTripModel::columnWidth(int) () > #1 0x000055555571fb96 in DiveListView::setupUi() () > #2 0x000055555571fdfe in DiveListView::reload(DiveTripModel::Layout, > bool) () > #3 0x000055555566168d in MainWindow::recreateDiveList() () > #4 0x000055555566ab21 in MainWindow::refreshDisplay(bool) () > #5 0x000055555566cb56 in MainWindow::loadFiles(QStringList) () > #6 0x000055555565d425 in main () > > If I start with an empty subsurface profile then all is fine until I add > a dive to the list at which point the segfault happens. > > Sorry I cannot help much more now. I'll try to clear some time tonight > (in about six hours) to try and actively investigate this... >
something else i would try is to modify this near line 430 in divelistview.cpp, from: DiveTripModel *tripModel = new DiveTripModel(this); to: tripModel = new DiveTripModel(this); out of ideas myself...and the crash shouldn't happen unless we are hitting a concurrency issue or something. lubomir -- _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
