Segfault - removing a device from list

[Rob Mason]

Hi - I'm using the PPA (AppImage has never worked for me).  The GDB output
is below. Hope this helps!  Thanks for the response.

Thread 1 "subsurface" received signal SIGSEGV, Segmentation fault.
0x0000000000666142 in DiveComputerModel::data(QModelIndex const&, int)
const ()
(gdb) bt 30
#0  0x0000000000666142 in DiveComputerModel::data(QModelIndex const&, int)
const ()
#1  0x00007ffff39e4d5d in  () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x00007fffe3c7dba6 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#3  0x00007ffff3a3548b in QTableView::selectionChanged(QItemSelection
const&, QItemSelection const&) ()
    at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x00007ffff3a00ab1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x00007ffff24d6d2a in QMetaObject::activate(QObject*, int, int, void**)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007ffff2458d27 in
QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection
const&) ()
    at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ffff2460e17 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff2461e09 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ffff24d6d2a in QMetaObject::activate(QObject*, int, int, void**)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff25530c4 in
QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int,
QAbstractItemModel::QPrivateSignal) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff244fc33 in QAbstractItemModel::beginRemoveRows(QModelIndex
const&, int, int) ()
    at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00000000006669a4 in DiveComputerModel::update() ()
#13 0x000000000066736d in DiveComputerModel::remove(QModelIndex const&) ()
#14 0x00000000005d5867 in
DiveComputerManagementDialog::tryRemove(QModelIndex const&) ()
#15 0x00007ffff24d6d2a in QMetaObject::activate(QObject*, int, int, void**)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff39f87f5 in QAbstractItemView::clicked(QModelIndex const&) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007ffff39fc7d3 in
QAbstractItemView::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007ffff37e2fc8 in QWidget::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007ffff38e1b8e in QFrame::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007ffff3a076db in QAbstractItemView::viewportEvent(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007ffff24a8172 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
    at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff37a003c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007ffff37a5c19 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007ffff24a838b in QCoreApplication::notifyInternal(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007ffff37a4b32 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007ffff37fd5bb in  () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007ffff37ffb7b in  () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x00007ffff37a005c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x00007ffff37a5516 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x00007ffff24a838b in QCoreApplication::notifyInternal(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb)

On 15 May 2018 at 14:11, Lubomir I. Ivanov <neolit123 at gmail.com> wrote:

> On 15 May 2018 at 15:59, Rob Mason <robmason38 at googlemail.com> wrote:
> > Hi,
> >
> > This is not a critical issue, but when clearing out some old backup dive
> > computers from my device list, I get a segfault straight after confirming
> > deletion. I'm using subsurface 4.7.8 on Mint Linux 18.3. Problem doesn't
> > appear on my Win10 laptop.
> >
>
> hi,
>
> i would have pointed you out towards our most recent development
> version, but it seems that our tooling did not build an AppImage:
> https://github.com/Subsurface-divelog/subsurface/releases/tag/continuous
>
> looking at this: https://subsurface-divelog.org/download/
> are you using the PPA build for Linux Mint or the AppImage one?
>
> you could do the following to provide us with more details about the crash
>
> see if GDB is present:
> gdb -v
>
> if not install it:
> sudo apt-get update
> sudo apt-get install gdb
>
> navigate to the subsurface binary folder and do:
> gdb ./subsurface
>
> to start the debugging type:
> r
>
> < make it crash via the UI >
>
> to obtain a backtrace call:
> bt 30
>
> share the output here.
>
> thanks
> lubomir
> --
> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180515/71e04ddb/attachment-0001.html>