• VLC on G5 crash : illegal instruction

    From Riccardo Mottola@21:1/5 to All on Sat Mar 6 14:40:02 2021
    Hi,

    I just tried VLC on a G5... it starts but as soon as I try to open a
    file, it dies "inside" the file selector! Not just a file, trying to
    click on my home directory, I get illegal instruction.ù

    If I give it a MP4 on the command line, it will come up and then die
    with illegal instruction.

    How does it work for you? and a G4? I will try there next week.

    Riccardo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to All on Sat Mar 6 15:30:01 2021
    Hello!

    On Mar 6, 2021, at 2:33 PM, Riccardo Mottola <riccardo.mottola@libero.it> wrote:


    I just tried VLC on a G5... it starts but as soon as I try to open a file, it dies "inside" the file selector! Not just a file, trying to click on my home directory, I get illegal instruction.ù

    If I give it a MP4 on the command line, it will come up and then die with illegal instruction.

    How does it work for you? and a G4? I will try there next week.

    Please install the dbgsym/dbg package for VLC and ffmpeg and provide a backtrace.

    Most likely someone added VSX support to either of them without guarding the code with #ifdefs.

    Adrian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Riccardo Mottola@21:1/5 to glaubitz@physik.fu-berlin.de on Sun Mar 7 19:30:01 2021
    Hi Adrian!


    On 2021-03-06 15:22:02 +0100 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:


    Please install the dbgsym/dbg package for VLC and ffmpeg and provide
    a
    backtrace.

    Most likely someone added VSX support to either of them without
    guarding the
    code with #ifdefs.

    the issue is most probably in libpcre2 or Qt5Core

    #0 0x00007fffe9c5fa30 in ?? ()
    #1 0x00007ffff02c406c in ?? () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #2 0x00007ffff02f3a38 in pcre2_jit_match_16 () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #3 0x00007ffff02f52b8 in pcre2_match_16 () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #4 0x00007ffff0ad0240 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #5 0x00007ffff0ad5a0c in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #6 0x00007ffff0ad5ffc in .QRegularExpression::match(QString const&,
    int, QRegularExpression::MatchType,
    QFlags<QRegularExpression::MatchOption>) const () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #7 0x00007ffff1ee41fc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #8 0x00007ffff1ee4fec in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #9 0x00007ffff1eeb6cc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #10 0x00007ffff0ce1618 in .QMetaCallEvent::placeMetaCall(QObject*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #11 0x00007ffff0ce7eec in .QObject::event(QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #12 0x00007ffff1eed8d8 in .QFileSystemModel::event(QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #13 0x00007ffff1beb5f4 in
    .QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #14 0x00007ffff1bf5c24 in .QApplication::notify(QObject*, QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #15 0x00007ffff0ca26bc in .QCoreApplication::notifyInternal2(QObject*,
    QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #16 0x00007ffff0ca2a54 in .QCoreApplication::sendEvent(QObject*,
    QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #17 0x00007ffff0ca6e64 in
    .QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
    QThreadData*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #18 0x00007ffff0ca74a4 in
    .QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #19 0x00007ffff0d2c048 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #20 0x00007ffff0165724 in g_main_context_dispatch () from /usr/lib/powerpc64-linux-gnu/libglib-2.0.so.0
    #21 0x00007ffff0165ab8 in ?? () from /usr/lib/powerpc64-linux-gnu/libglib-2.0.so.0
    #22 0x00007ffff0165bd0 in g_main_context_iteration () from /usr/lib/powerpc64-linux-gnu/libglib-2.0.so.0
    #23 0x00007ffff0d2af24 in .QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
    ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #24 0x00007fffeb710f24 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5XcbQpa.so.5
    #25 0x00007ffff0c9f540 in .QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #26 0x00007ffff0c9fcac in .QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #27 0x00007ffff1ebb5ec in .QDialog::exec() () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #28 0x00007ffff1ed5768 in .QFileDialog::getOpenFileUrls(QWidget*,
    QString const&, QUrl const&, QString const&, QString*, QFlags<QFileDialog::Option>, QStringList const&) () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #29 0x00007ffff24d73ec in ?? () from /usr/lib/powerpc64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
    #30 0x00007ffff24d9b64 in ?? () from /usr/lib/powerpc64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
    #31 0x00007ffff24dae28 in ?? () from /usr/lib/powerpc64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
    #32 0x00007ffff2674f44 in ?? () from /usr/lib/powerpc64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
    #33 0x00007ffff0cf7084 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5


    --
    Sent with GNUMail from iMac PowerPC 64bit running GNUstep on Debian/PPC

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Riccardo Mottola on Sun Mar 7 19:40:02 2021
    Hello!

    On 3/7/21 7:25 PM, Riccardo Mottola wrote:
    Most likely someone added VSX support to either of them without guarding the code with #ifdefs.

    the issue is most probably in libpcre2 or Qt5Core

    #0 0x00007fffe9c5fa30 in ?? ()
    #1 0x00007ffff02c406c in ?? () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #2 0x00007ffff02f3a38 in pcre2_jit_match_16 () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #3 0x00007ffff02f52b8 in pcre2_match_16 () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0
    #4 0x00007ffff0ad0240 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #5 0x00007ffff0ad5a0c in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5

    Could you install all the pcre2 dbgsym packages [1] and try again?

    With the dbgsym packages, we would get a backtrace with code references.

    Adrian

    [1] http://ftp.ports.debian.org/debian-ports/pool-ppc64/main/p/pcre2/

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luke Kenneth Casson Leighton@21:1/5 to All on Sun Mar 7 20:20:02 2021
    On Sunday, March 7, 2021, Riccardo Mottola <riccardo.mottola@libero.it>
    wrote:.


    the issue is most probably in libpcre2 or Qt5Core

    #0 0x00007fffe9c5fa30 in ?? ()
    #1 0x00007ffff02c406c in ?? () from /usr/lib/powerpc64-linux-gnu/l ibpcre2-16.so.0



    https://vcs.pcre.org/pcre2/code/trunk/src/sljit/sljitNativePPC_common.c?revision=1268&view=markup

    *splutter* but... but... wow! that's amazing. pcre2 contains a JIT
    assembly compiler simply for the purposes of generating highly optimised regular expression parsing.

    holy cow :)

    chances are then that an instruction was added which is assumed to exist in OpenPOWER v3.0 but is not present in v2.06 (etc)

    a cursory scan shows no evidence of the use of VSX there.

    l.



    --
    ---
    crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

    <br><br>On Sunday, March 7, 2021, Riccardo Mottola &lt;<a href="mailto:riccardo.mottola@libero.it">riccardo.mottola@libero.it</a>&gt; wrote:.<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

    the issue is most probably in libpcre2 or Qt5Core<br>

    #0  0x00007fffe9c5fa30 in ?? ()<br>
    #1  0x00007ffff02c406c in ?? () from /usr/lib/powerpc64-linux-gnu/l<wbr>ibpcre2-16.so.0</blockquote><div><br></div><div><br></div><div><span style="font-size:15px"><a href="https://vcs.pcre.org/pcre2/code/trunk/src/sljit/sljitNativePPC_common.c?revision=
    1268&amp;view=markup">https://vcs.pcre.org/pcre2/code/trunk/src/sljit/sljitNativePPC_common.c?revision=1268&amp;view=markup</a></span></div><div><span style="font-size:15px"><br></span></div><div><span style="font-size:15px">*splutter* but... but... wow!
    that&#39;s amazing.  pcre2 contains a JIT assembly compiler simply for the purp
  • From Jeffrey Walton@21:1/5 to lkcl@lkcl.net on Mon Mar 8 09:40:02 2021
    On Sun, Mar 7, 2021 at 2:10 PM Luke Kenneth Casson Leighton
    <lkcl@lkcl.net> wrote:

    On Sunday, March 7, 2021, Riccardo Mottola <riccardo.mottola@libero.it> wrote:.

    the issue is most probably in libpcre2 or Qt5Core

    #0 0x00007fffe9c5fa30 in ?? ()
    #1 0x00007ffff02c406c in ?? () from /usr/lib/powerpc64-linux-gnu/libpcre2-16.so.0

    https://vcs.pcre.org/pcre2/code/trunk/src/sljit/sljitNativePPC_common.c?revision=1268&view=markup

    *splutter* but... but... wow! that's amazing. pcre2 contains a JIT assembly compiler simply for the purposes of generating highly optimised regular expression parsing.

    holy cow :)

    chances are then that an instruction was added which is assumed to exist in OpenPOWER v3.0 but is not present in v2.06 (etc)

    a cursory scan shows no evidence of the use of VSX there.

    If needed... I believe it is possible to disable PCRE2's JIT at configure time.

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Jeffrey Walton on Mon Mar 8 10:00:01 2021
    On 3/8/21 9:38 AM, Jeffrey Walton wrote:
    a cursory scan shows no evidence of the use of VSX there.

    If needed... I believe it is possible to disable PCRE2's JIT at configure time.

    We certainly shouldn't disable the whole JIT over a single instruction but rather
    check whether this instruction can be guarded on older POWER systems.

    But we need to find out first which instruction triggers the SIGILL.

    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luke Kenneth Casson Leighton@21:1/5 to glaubitz@physik.fu-berlin.de on Mon Mar 8 12:10:02 2021
    On Mon, Mar 8, 2021 at 8:50 AM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:

    On 3/8/21 9:38 AM, Jeffrey Walton wrote:
    a cursory scan shows no evidence of the use of VSX there.

    If needed... I believe it is possible to disable PCRE2's JIT at configure time.

    We certainly shouldn't disable the whole JIT over a single instruction but rather
    check whether this instruction can be guarded on older POWER systems.

    But we need to find out first which instruction triggers the SIGILL.

    forgot to say, gdb will have a command that prints out the raw binary
    being executed and may also run disassembly on it.

    https://sourceware.org/gdb/onlinedocs/gdb/Backtrace.html

    display/i $pc might do it

    disas /r /m $pc

    or

    disas /r /m $pc-8

    l.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Riccardo Mottola@21:1/5 to John Paul Adrian Glaubitz on Sun Mar 14 20:00:02 2021
    Hi,

    On 3/8/21 9:49 AM, John Paul Adrian Glaubitz wrote:
    We certainly shouldn't disable the whole JIT over a single instruction but rather
    check whether this instruction can be guarded on older POWER systems.

    But we need to find out first which instruction triggers the SIGILL.

    Indeed, it crashes inside JIT, here the stacktrace:

    #0  0x00007fffe9c5fa30 in ?? ()
    #1  0x00007ffff02c406c in jit_machine_stack_exec (arguments=arguments@entry=0x7fffeb9a51d8,
        executable_func=0x7fffe9c5fd00) at src/pcre2_jit_match.c:57
    #2  0x00007ffff02f3a38 in pcre2_jit_match_16 (code=0x7fffec4392a0, subject=0x100165218,
        length=<optimized out>, start_offset=<optimized out>, options=<optimized out>,
        match_data=0x7fffec3cd180, mcontext=<optimized out>) at src/pcre2_jit_match.c:168
    #3  0x00007ffff02f52b8 in pcre2_match_16 (code=0x7fffec4392a0, subject=0x100165218, length=37,
        start_offset=0, options=0, match_data=0x7fffec3cd180, mcontext=0x1001782c0) at src/pcre2_match.c:6345
    #4  0x00007ffff0ad0240 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #5  0x00007ffff0ad5a0c in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #6  0x00007ffff0ad5ffc in .QRegularExpression::match(QString const&,
    int, QRegularExpression::MatchType,
    QFlags<QRegularExpression::MatchOption>) const () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #7  0x00007ffff1ee41fc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #8  0x00007ffff1ee4fec in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #9  0x00007ffff1eeb6cc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #10 0x00007ffff0ce1618 in .QMetaCallEvent::placeMetaCall(QObject*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #11 0x00007ffff0ce7eec in .QObject::event(QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #12 0x00007ffff1eed8d8 in .QFileSystemModel::event(QEvent*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #13 0x00007ffff1beb5f4 in .QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #14 0x00007ffff1bf5c24 in .QApplication::notify(QObject*, QEvent*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #15 0x00007ffff0ca26bc in .QCoreApplication::notifyInternal2(QObject*,
    QEvent*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #16 0x00007ffff0ca2a54 in .QCoreApplication::sendEvent(QObject*, QEvent*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #17 0x00007ffff0ca6e64 in
    .QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
       from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5

    (gdb) p local_stack
    $1 = {top = 0x7fffeb9a5158 "", end = 0x7fffeb9a5158 "", start =
    0x7fffeb99d158 "",
      min_start = 0x7fffeb99d158 ""}

    (gdb) p *arguments
    $3 = {stack = 0x7fffeb99d138, str = 0x100165218, begin = 0x100165218,
    end = 0x100165262,
      match_data = 0x7fffec3cd180, startchar_ptr = 0x100165218, mark_ptr =
    0x0, callout = 0x0,
      callout_data = 0x0, offset_limit = 18446744073709551615, limit_match
    = 10000000, oveccount = 2,
      options =


    (gdb) p arguments->str
    $4 = (PCRE2_SPTR16) 0x100165218
    (gdb) p arguments->startchar_ptr
    $5 = (PCRE2_SPTR16) 0x100165218
    (gdb) p arguments->stack
    $6 = (struct sljit_stack *) 0x7fffeb99d138
    (gdb) p arguments->begin
    $7 = (PCRE2_SPTR16) 0x100165218
    (gdb)

    Now... I am not much wiser, I hope you will be!


    Riccardo


    PS: there is risk that due to stronger lock-down I might not access this machine for a fortnight or more.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeffrey Walton@21:1/5 to riccardo.mottola@libero.it on Sun Mar 14 20:40:01 2021
    On Sun, Mar 14, 2021 at 2:57 PM Riccardo Mottola
    <riccardo.mottola@libero.it> wrote:

    On 3/8/21 9:49 AM, John Paul Adrian Glaubitz wrote:
    We certainly shouldn't disable the whole JIT over a single instruction but rather
    check whether this instruction can be guarded on older POWER systems.

    But we need to find out first which instruction triggers the SIGILL.

    Indeed, it crashes inside JIT, here the stacktrace:

    #0 0x00007fffe9c5fa30 in ?? ()
    #1 0x00007ffff02c406c in jit_machine_stack_exec (arguments=arguments@entry=0x7fffeb9a51d8,
    executable_func=0x7fffe9c5fd00) at src/pcre2_jit_match.c:57
    #2 0x00007ffff02f3a38 in pcre2_jit_match_16 (code=0x7fffec4392a0, subject=0x100165218,
    length=<optimized out>, start_offset=<optimized out>,
    options=<optimized out>,
    match_data=0x7fffec3cd180, mcontext=<optimized out>) at src/pcre2_jit_match.c:168
    #3 0x00007ffff02f52b8 in pcre2_match_16 (code=0x7fffec4392a0, subject=0x100165218, length=37,
    start_offset=0, options=0, match_data=0x7fffec3cd180, mcontext=0x1001782c0) at src/pcre2_match.c:6345
    #4 0x00007ffff0ad0240 in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #5 0x00007ffff0ad5a0c in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #6 0x00007ffff0ad5ffc in .QRegularExpression::match(QString const&,
    int, QRegularExpression::MatchType,
    QFlags<QRegularExpression::MatchOption>) const () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #7 0x00007ffff1ee41fc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #8 0x00007ffff1ee4fec in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #9 0x00007ffff1eeb6cc in ?? () from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #10 0x00007ffff0ce1618 in .QMetaCallEvent::placeMetaCall(QObject*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #11 0x00007ffff0ce7eec in .QObject::event(QEvent*) () from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #12 0x00007ffff1eed8d8 in .QFileSystemModel::event(QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #13 0x00007ffff1beb5f4 in .QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #14 0x00007ffff1bf5c24 in .QApplication::notify(QObject*, QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Widgets.so.5
    #15 0x00007ffff0ca26bc in .QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #16 0x00007ffff0ca2a54 in .QCoreApplication::sendEvent(QObject*, QEvent*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5
    #17 0x00007ffff0ca6e64 in .QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
    from /usr/lib/powerpc64-linux-gnu/libQt5Core.so.5

    (gdb) p local_stack
    $1 = {top = 0x7fffeb9a5158 "", end = 0x7fffeb9a5158 "", start = 0x7fffeb99d158 "",
    min_start = 0x7fffeb99d158 ""}

    (gdb) p *arguments
    $3 = {stack = 0x7fffeb99d138, str = 0x100165218, begin = 0x100165218,
    end = 0x100165262,
    match_data = 0x7fffec3cd180, startchar_ptr = 0x100165218, mark_ptr =
    0x0, callout = 0x0,
    callout_data = 0x0, offset_limit = 18446744073709551615, limit_match
    = 10000000, oveccount = 2,
    options =

    You probably need to go to frame 1 ('f 1' under gdb) and disassemble
    ('disass .' or 'disass' followed by a bunch of pages). That will show
    the offending instruction.

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luke Kenneth Casson Leighton@21:1/5 to noloader@gmail.com on Sun Mar 14 23:00:02 2021
    ---
    crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

    On Sun, Mar 14, 2021 at 7:34 PM Jeffrey Walton <noloader@gmail.com> wrote:

    You probably need to go to frame 1 ('f 1' under gdb) and disassemble
    ('disass .' or 'disass' followed by a bunch of pages). That will show
    the offending instruction.

    yes. because it's a JIT it's not the stack that's needed so much as
    the actual instruction at the actual PC. it won't be the
    statically-compiled program, because that program *created* the
    program (JIT compiled) currently being run.

    l.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)