Re: 2.4 crash report

[Jean-Marc Lasgouttes]

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

[Wolfgang Engelmann]

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

[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
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Wolfgang Engelmann]

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

[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


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Wolfgang Engelmann]

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 0x0

Re: 2.4 crash report

[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.

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

[Wolfgang Engelmann]

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

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> That did the trick! I applied the patch, rebuilt the tarball, and re-ran
> the SlackBuild script. Re-installed the application and it imported the
> text file as usual.

Excellent.

>    I still have a few keyboard quirks to fix (e.g., pressing the [Del] key
> displays the spade card suit image rather than deleting the space after the
> point), but I'll get those worked out.
>
>    Will you apply the patch to the source tarball on the web site?

It's already applied to what will become LyX 1.6.2 eventually.

Jürgen

Re: Crash Report: 1.6.1 on Linux

[Rich Shepard]

On Fri, 9 Jan 2009, Jürgen Spitzmüller wrote:


No, I was referring to the File filter list set by LyX for this file dialog. I
assume you are building LyX yourself. Could you apply the attached patch and
check if this helps?


Jürgen,

  That did the trick! I applied the patch, rebuilt the tarball, and re-ran
the SlackBuild script. Re-installed the application and it imported the text
file as usual.

  I still have a few keyboard quirks to fix (e.g., pressing the [Del] key
displays the spade card suit image rather than deleting the space after the
point), but I'll get those worked out.

  Will you apply the patch to the source tarball on the web site?

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> I assume that you refer to the file filters on my system. 

No, I was referring to the File filter list set by LyX for this file dialog. I 
assume you are building LyX yourself. Could you apply the attached patch and 
check if this helps?

(to apply: put the file in the uppermost folder of the lyx source tree, i.e. 
above "src", issue "patch -p0 < x.diff" and then rebuild with "make").

>    After cleaning these up, if it still crashes I'll run a backtrace and
> post the output.

Yes, please.

> Thanks,
>
> Rich

Jürgen
Index: src/frontends/qt4/GuiView.cpp
===
--- src/frontends/qt4/GuiView.cpp	(Revision 28032)
+++ src/frontends/qt4/GuiView.cpp	(Arbeitskopie)
@@ -1626,7 +1626,7 @@
 		LFUN_FILE_INSERT_PLAINTEXT_PARA : LFUN_FILE_INSERT_PLAINTEXT));
 
 	FileDialog::Result result = dlg.open(toqstr(bv->buffer().filePath()),
-		QStringList());
+		QStringList(qt_("All Files (*)")));
 
 	if (result.first == FileDialog::Later)
 		return;

Re: Crash Report: 1.6.1 on Linux

[Rich Shepard]

On Thu, 8 Jan 2009, Jürgen Spitzmüller wrote:


Doesn't crash for me. However, the file filters are not correctly set.


Jürgen,

  I assume that you refer to the file filters on my system. When I navigate
to Edit -> Preferences -> File handling I see two choices: Converters and
File Formats. The former has no entry for plain text, the latter seems to
specify conversions for import using ps2text and the like. What should I be
looking for?


You should run LyX from within gdb.


  OK. Here is the output before starting the backtrace. I need to clean
these up first:

LyX: BN_BIND: Unknown LyX function ont-code"' [around line 7 of file
~/.lyx/bind/my.bind current token: 'font-code"' context: '']

(NB: I checked the RELEASE_NOTES and changed the above to 'font-typewriter'
in ~/.lyx/bind/my.bind, but it's apparently not being seen. In the
following, I've not found the strings in the RELEASE_NOTES so I've no idea
how to fix them.)

LyX: BN_BIND: Unknown LyX function `hfill-insert' [around line 22 of file
~/.lyx/bind/my.bind current token: 'hfill-insert' context: '']
LyX: BN_BIND: Unknown LyX function `find-replace' [around line 33 of file
~/.lyx/bind/my.bind current token: 'find-replace' context: '']
LyX: BN_BIND: Unknown LyX function `layout-paste' [around line 46 of file
~/.lyx/bind/my.bind current token: 'layout-paste' context: '']
LyX: Unknown tag bing' [around line 64 of file ~/.lyx/bind/my.bind current
token: '\bing' context: '']
LyX: BN_BIND: Unknown LyX function `vc-history' [around line 69 of file
~/.lyx/bind/my.bind current token: 'vc-history' context: '']
LyX: Unknown tag ind' [around line 110 of file ~/.lyx/bind/my.bind current
token: 'bind' context: '']
LyX: BN_BIND: Unknown LyX function `reference-goto' [around line 131 of file
~/.lyx/bind/my.bind current token: 'reference-goto' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 151 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `backward-select' [around line 152 of file
~/
.lyx/bind/my.bind current token: 'backward-select' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 153 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `break-paragraph-keep-layout' [around line
177 of file ~/.lyx/bind/my.bind current token: 'break-paragraph-keep-layout'
context: '']
LyX: BN_BIND: Unknown LyX function `ligature-break-insert' [around line 179
of file ~/.lyx/bind/my.bind current token: 'ligature-break-insert' context:
'']
LyX: BN_BIND: Unknown LyX function `protected-space-insert' [around line 180
of file ~/.lyx/bind/my.bind current token: 'protected-space-insert' context:
'']
LyX: BN_BIND: Unknown LyX function nd-of-sentence-period-insert' [around
line 181 of file ~/.lyx/bind/my.bind current token:
'end-of-sentence-period-insert' context: '']

(NB: found the following and replaced the string in the .bind file.)

LyX: BN_BIND: Unknown LyX function `dots-insert' [around line 182 of file
~/.lyx/bind/my.bind current token: 'dots-insert' context: '']
LyX: BN_BIND: Unknown LyX function `layout-copy' [around line 184 of file
~/.lyx/bind/my.bind current token: 'layout-copy' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 188 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `backward-select' [around line 189 of file
~/.lyx/bind/my.bind current token: 'backward-select' context: '']
KeyMap.cpp(227): KeyMap::read: error while reading bind
file:/home/rshepard/.lyx/bind/my.bind
Error: New binding for 'Ctrl+D Del' is overriding old binding...
Menus.cpp(588): Menu warning: menu entries "Ordinary Quote|O" and
"Horizontal Space...|o" share the same shortcut.
Menus.cpp(588): Menu warning: menu entries "Ordinary Quote|O" and
"Horizontal Space...|o" share the same shortcut.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6f378e0 (LWP 26049)]
qt_clean_filter_list (filt...@0x87bebb4)
at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:70
70  ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h: No such
file or directory.
in ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h
Current language:  auto; currently c++

  After cleaning these up, if it still crashes I'll run a backtrace and post
the output.

Thanks,

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> Open existing document. Select from menu Insert -> Insert File -> Plain
> text join lines (or just Plain text). Instant crash; lyx shuts down.

Doesn't crash for me. However, the file filters are not correctly set.

> Invoking from the command line with the -dbg switch tells me only what
> features can be debugged, it doesn't run the application in a debugger.

You should run LyX from within gdb. See
http://wiki.lyx.org/FAQ/FurtherHelp#toc4

Jürgen

Crash Report: 1.6.1 on Linux

[Rich Shepard]

  Cue the music, please. This is a repeatable error -- a fatal flaw, in fact
-- with lyx-1.6.1 on Slackware-12.1.

  Open existing document. Select from menu Insert -> Insert File -> Plain
text join lines (or just Plain text). Instant crash; lyx shuts down.
Invoking from the command line with the -dbg switch tells me only what
features can be debugged, it doesn't run the application in a debugger.

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report

[Rich Shepard]

On Fri, 26 May 2006, Georg Baum wrote:


If the cursor was inside a table during the class change then this is a
known bug that is already fixed in 1.4.2svn.


Georg,

  It may well have been that situation. I set up a 2 row/1 column table in
the title environment so I could put the company logo above the title.

  I know there's another way of doing this with the titlehead environment in
the Koma-script classes, but the doc didn't make clear how to do that, and my
trial and error attempts failed to produce what I wanted.

  Glad it's fixed and my message was superfluous.

Rich

--
Richard B. Shepard, Ph.D. |  The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)  |  Accelerator
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report

[Georg Baum]

Rich Shepard wrote:

>Situation: LyX-1.4.1 on Slackware-10.2/teTeX-3.0-i486-2_10.2. Document
> type was Koma-report and I changed it to article. As soon as I clicked on
> the Apply button the application instantly shut down.
> 
>Re-invoked it and opened the emergency save. Just thought you
>developers
> would like to be aware of what happened. I cannot recall LyX crashing on
> me before.

If the cursor was inside a table during the class change then this is a
known bug that is already fixed in 1.4.2svn.


Georg

Crash Report

[Rich Shepard]

  Situation: LyX-1.4.1 on Slackware-10.2/teTeX-3.0-i486-2_10.2. Document
type was Koma-report and I changed it to article. As soon as I clicked on the
Apply button the application instantly shut down.

  Re-invoked it and opened the emergency save. Just thought you developers
would like to be aware of what happened. I cannot recall LyX crashing on me
before.

Rich

--
Richard B. Shepard, Ph.D. |  The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)  |  Accelerator
 Voice: 503-667-4517  Fax: 503-667-8863