-
Notifications
You must be signed in to change notification settings - Fork 157
Crash on Undo after erasing of any atom with attached H's #547
Comments
Seems like you're submitting backtraces from binaries without debug information - not useful at all (everything interesting is in ??) Original comment by: @annulen |
If the stack frame doesn't help, just ignore it then. Original comment by: @mbanck |
This is the full backtrace, as recorded by the user who also reported the other crasher:
Original comment by: @mbanck |
That full backtrace has been recorded using master, not 1.0.1. Original comment by: @mbanck |
Thank you! I've realized that stack trace is not useful in this case because crash is caused by exception, which unwinds the stack. Original comment by: @annulen |
Crash on undo occurs after erasing (right click in drawtool) of any atom with attached H's, e.g., methyl group, if "Adjust hydrogens" is enabled at the moment of right click Original comment by: @annulen |
Fix submitted to Gerrit Original comment by: nobody |
So this looks like it is fixed in 1.0, I have cherry picked these into master too. I am marking this issue as resolved - these fixes will make it into the upcoming release. Original comment by: @cryos |
This is with version 1.0.1 (which still does not exist in the "Group" dropdown on the SF bug tracker)
Reproduce:
Backtrace:
(gdb) bt
#0 0xb7fe2424 in __kernel_vsyscall ()
#1 0xb7eaa751 in raise () from /lib/i686/cmov/libc.so.6
#2 0xb7eadb82 in abort () from /lib/i686/cmov/libc.so.6
#3 0xb6c2453f in gnu_cxx::verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#4 0xb6c22405 in ?? () from /usr/lib/libstdc++.so.6
#5 0xb6c22442 in std::terminate() () from /usr/lib/libstdc++.so.6
#6 0xb6c224fb in cxa_rethrow () from /usr/lib/libstdc++.so.6
#7 0xb701c512 in QCoreApplication::notifyInternal(QObject, QEvent) () from /usr/lib/libQtCore.so.4
#8 0xb7292a52 in QApplicationPrivate::sendMouseEvent(QWidget, QMouseEvent, QWidget, QWidget, QWidget**, QPointer&, bool) () from /usr/lib/libQtGui.so.4
#9 0xb731e298 in ?? () from /usr/lib/libQtGui.so.4
#10 0xb731d283 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb734b3c2 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb699b305 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#13 0xb699efe8 in ?? () from /lib/libglib-2.0.so.0
#14 0xb699f1c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#15 0xb70480a5 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4
#16 0xb734af25 in ?? () from /usr/lib/libQtGui.so.4
#17 0xb701ab19 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4
#18 0xb701af6a in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4
#19 0xb702019f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#20 0xb728c667 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#21 0x08072763 in ?? ()
#22 0xb7e96c76 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#23 0x08061741 in _start ()
Reported by: @mbanck
The text was updated successfully, but these errors were encountered: