Re: 2.4 crash report
Le 12/03/2023 à 15:18, Wolfgang Engelmann a écrit : Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes: Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit : did I send the correct infos? I am still not sure what I should do in case of a crash in gdb. Was 'where' helpful? I did not find the output very useful, but it is probably not you fault. Is the problem reproducible? What were you doing at the time of the freeze? If you can reproduce, it would be nice to know whether you can obtain a different backtrace. JMarc whether you can obtain a > different backtrace. you mean instead of using gdb? Or rather in a different run. You say that LyX is frozen, does this mean that you have to abort it yourself? Another possibility is to run LyX under a tool like valgrind (which detects memory errors before they cause crashes). JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: 2.4 crash report
Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes: Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit : did I send the correct infos? I am still not sure what I should do in case of a crash in gdb. Was 'where' helpful? I did not find the output very useful, but it is probably not you fault. Is the problem reproducible? What were you doing at the time of the freeze? If you can reproduce, it would be nice to know whether you can obtain a different backtrace. JMarc whether you can obtain a > different backtrace. you mean instead of using gdb? Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: 2.4 crash report
Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit : did I send the correct infos? I am still not sure what I should do in case of a crash in gdb. Was 'where' helpful? I did not find the output very useful, but it is probably not you fault. Is the problem reproducible? What were you doing at the time of the freeze? If you can reproduce, it would be nice to know whether you can obtain a different backtrace. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: 2.4 crash report
Am 12.03.23 um 01:42 schrieb Richard Kimberly Heck: On 3/11/23 08:05, Wolfgang Engelmann wrote: This I got in the terminal and in the gdb Wolfgang >>> insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible command name Standard. That will lead to an assertion, at least. It also should not happen. "Standard" sounds like a layout name that has been somehow construed as an inset parameter. Riki did I send the correct infos? I am still not sure what I should do in case of a crash in gdb. Was 'where' helpful? Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: 2.4 crash report
On 3/11/23 08:05, Wolfgang Engelmann wrote: This I got in the terminal and in the gdb Wolfgang >>> insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible command name Standard. That will lead to an assertion, at least. It also should not happen. "Standard" sounds like a layout name that has been somehow construed as an inset parameter. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: 2.4 crash report
Am 11.03.23 um 13:31 schrieb José Matos: On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote: To whom should I report a 2.4.0 crash? I use Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022) Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb) Qt-Version (bei Erstellung): 5.15.2 OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye) Python-Aufruf: python3 -tt and started the document with gdb lyx2.4.0 run Symptom: The document was frozen, I got infos from the terminal which I could send on request Wolfgang What do you get when you "bt" that corresponds to backtrace. where should I say bt? Or it simply froze and there is no feedback? yes, it was frozen, I had to stop the gdb Best regards, This I got in the terminal and in the gdb Wolfgang >>> insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible command name Standard. Warning: Befehl für Einfügung: Inkompatibler Befehlsname. [Thread 0x7fffc087d700 (LWP 5536) exited] [Thread 0x7fff9f7fe700 (LWP 5535) exited] [Thread 0x7fff9700 (LWP 5534) exited] [Thread 0x7fff9e7fc700 (LWP 5533) exited] Empty filename passed to function Empty filename passed to function ## [Thread 0x7fff9700 (LWP 5657) exited] ^C--Type for more, q to quit, c to continue without paging--c Thread 1 "lyx2.4.0" received signal SIGINT, Interrupt. futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) at ../sysdeps/nptl/f utex-internal.h:186 186 ../sysdeps/nptl/futex-internal.h: Datei oder Verzeichnis nicht gefunden. (gdb) ## . (gdb) where #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) at ../sysdeps/nptl/futex-internal.h:186 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5633cc48, cond=0x7fffd460) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fffd460, mutex=0x5633cc48) at pthread_cond_wait.c:638 #3 0x73ed9edf in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x73edbd7f in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #5 0x73edbe91 in xcb_wait_for_reply () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #6 0x735c4eaa in QXcbConnection::sync() () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7 0x735dbea3 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x735dc2c0 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x77499abe in QBackingStore::beginPaint(QRegion const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x779d36a2 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x77a036d7 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 --Type for more, q to quit, c to continue without paging-- ## ] ^C--Type for more, q to quit, c to continue without paging--c Thread 1 "lyx2.4.0" received signal SIGINT, Interrupt. futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) at ../sysdeps/nptl/f utex-internal.h:186 186 ../sysdeps/nptl/futex-internal.h: Datei oder Verzeichnis nicht gefunden. (gdb) where #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) at ../sysdeps/nptl/futex-internal.h:186 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5633cc48, cond=0x7fffd460) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fffd460, mutex=0x5633cc48) at pthread_cond_wait.c:638 #3 0x73ed9edf in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x73edbd7f in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #5 0x73edbe91 in xcb_wait_for_reply () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #6 0x735c4eaa in QXcbConnection::sync() () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7 0x735dbea3 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x735dc2c0 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x77499abe in QBackingStore::beginPaint(QRegion const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x779d36a2 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x77a036d7 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 --Type for more, q to quit, c to continue without paging--c #12 0x779c315f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/li b/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x55d984d9 in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) (this=0x55 555631d390, receiver=, event=) at GuiApplication.cpp:2998 #14 0x76efefca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib /x86_64-linux-gnu/libQt5Core.so.5 #15 0x76f01a01 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadDat a*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x76f56e93 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17
Re: 2.4 crash report
On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote: > To whom should I report a 2.4.0 crash? > I use > Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022) > Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb) > Qt-Version (bei Erstellung): 5.15.2 > OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye) > Python-Aufruf: python3 -tt > > and started the document with > gdb lyx2.4.0 > run > > Symptom: The document was frozen, I got infos from the terminal which > I > could send on request > > Wolfgang What do you get when you "bt" that corresponds to backtrace. Or it simply froze and there is no feedback? Best regards, -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
2.4 crash report
To whom should I report a 2.4.0 crash? I use Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022) Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb) Qt-Version (bei Erstellung): 5.15.2 OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye) Python-Aufruf: python3 -tt and started the document with gdb lyx2.4.0 run Symptom: The document was frozen, I got infos from the terminal which I could send on request Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
