Somewhat random ideas based on this "sounding" like a problem with this document since other docs compile w/o a problem:

If you have a backup copy, or two, try them and see if they work.

Try divide and conquer. Save half of the doc as two other docs and see if they compile. Rinse and repeat if only one fails until you isolate a region that is a problem. That can then be recreated.

I am NOT a LyX (or LaTeX user so YMMV.

~~R

On 1/18/24 09:44, Rich Shepard wrote:
I've not had this issue in the 25 years I've been writing LaTeX in LyX. When
I try to compile it (using pdflatex) it segfaults with these details:

(  1) /usr/bin/lyx: /usr/bin/lyx() [0x981cd5]
(  2) /usr/bin/lyx: /usr/bin/lyx() [0x9f5032]
(  3) /usr/lib64/libQtCore.so.4: QObject::event(QEvent*)
(  4) /usr/lib64/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(  5) /usr/lib64/libQtGui.so.4: QApplication::notify(QObject*, QEvent*)
(  6) /usr/bin/lyx: /usr/bin/lyx() [0x997386]
(  7) /usr/lib64/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, QEvent*) (  8) /usr/lib64/libQtCore.so.4: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (  9) /usr/lib64/libQtCore.so.4: /usr/lib64/libQtCore.so.4(+0x1bef3e) [0x7fa06b936f3e] ( 10) /usr/lib64/libglib-2.0.so.0: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x287) [0x7fa06d548787] ( 11) /usr/lib64/libglib-2.0.so.0: /usr/lib64/libglib-2.0.so.0(+0x489b8) [0x7fa06d5489b8] ( 12) /usr/lib64/libglib-2.0.so.0: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fa06d548a5c] ( 13) /usr/lib64/libQtCore.so.4: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ( 14) /usr/lib64/libQtGui.so.4: /usr/lib64/libQtGui.so.4(+0x2a29e6) [0x7fa06bf149e6] ( 15) /usr/lib64/libQtCore.so.4: QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ( 16) /usr/lib64/libQtCore.so.4: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
( 17) /usr/lib64/libQtCore.so.4: QCoreApplication::exec()
( 18) /usr/bin/lyx: /usr/bin/lyx() [0x5f667d]
( 19) /usr/bin/lyx: /usr/bin/lyx() [0x469816]
( 20) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7fa06a5d97d0]
( 21) /usr/bin/lyx: /usr/bin/lyx() [0x475e89]

When I click the OK button it kills the LyX process and removes all open
document tabs. This same document compiled just fine several months ago, but I need to modify it and hit this issue yesterday. Both yesterday and today
other docs compile without causing a segfault.

I'm totally stumped. I've no idea how to isolate the reason for this,
especially since there are four new (last month) DIMMs in this host. Should
I re-write the doc from scratch?

Thoughts appreciated,

Rich

Reply via email to