• Kernel: Bad RIP value

    From Grimble@2:250/1 to All on Fri Jul 31 15:11:26 2020
    Syslog contains ONLY pairs of messages as follows:
    Jul 31 00:00:01 bach kernel: [200588.032271] pl[8592]: segfault at
    30332d3730 ip 00000030332d3730 sp 00007ffd07808d30 error 14
    Jul 31 00:00:01 bach kernel: [200588.032277] Code: Bad RIP value.

    Repeated at 5 minute intervals.
    My crontab starts a Python program every 5 minutes. During execution,
    the program calls an external program, ploticus, referenced as '/usr/local/bin/pl'. pl was built from source in September 2018 and has
    not been updated.
    Am I correct connecting the name of the executable to the "pl" in the
    first message?
    What is a RIP value?
    What would be a good RIP value?
    Can anyone shed further light on how to correct the problem?

    Thanks,
    Grimble
    Registered Linux User #450547
    Machine 'Bach' running Plasma 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri Jul 31 16:00:52 2020
    On Fri, 31 Jul 2020 10:11:26 -0400, Grimble <grimble@nomail.afraid.org> wrote:

    Syslog contains ONLY pairs of messages as follows:
    Jul 31 00:00:01 bach kernel: [200588.032271] pl[8592]: segfault at
    30332d3730 ip 00000030332d3730 sp 00007ffd07808d30 error 14
    Jul 31 00:00:01 bach kernel: [200588.032277] Code: Bad RIP value.
    Repeated at 5 minute intervals.
    My crontab starts a Python program every 5 minutes. During execution,
    the program calls an external program, ploticus, referenced as '/usr/local/bin/pl'. pl was built from source in September 2018 and has
    not been updated.
    Am I correct connecting the name of the executable to the "pl" in the
    first message?

    Yes.

    What is a RIP value?

    The register containing the instruction pointer register.

    What would be a good RIP value?

    A pointer that is within the range used by the code segment.

    Can anyone shed further light on how to correct the problem?

    You can try running it under gdb, but as the project doesn't have a bugzilla page, or appear to be actively under development, you'll have to figure out
    how to fix it yourself.

    It may be exceeding one of the limits explained at http://ploticus.sourceforge.net/doc/limits.html

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From grimble@2:250/1 to All on Wed Aug 5 00:24:55 2020
    On 31/07/2020 16:00, David W. Hodgins wrote:
    On Fri, 31 Jul 2020 10:11:26 -0400, Grimble <grimble@nomail.afraid.org> wrote:

    Syslog contains ONLY pairs of messages as follows:
    Jul 31 00:00:01 bach kernel: [200588.032271] pl[8592]: segfault at
    30332d3730 ip 00000030332d3730 sp 00007ffd07808d30 error 14
    Jul 31 00:00:01 bach kernel: [200588.032277] Code: Bad RIP value.
    Repeated at 5 minute intervals.
    My crontab starts a Python program every 5 minutes. During execution,
    the program calls an external program, ploticus, referenced as
    '/usr/local/bin/pl'. pl was built from source in September 2018 and has
    not been updated.
    Am I correct connecting the name of the executable to the "pl" in the
    first message?

    Yes.

    What is a RIP value?

    The register containing the instruction pointer register.

    What would be a good RIP value?

    A pointer that is within the range used by the code segment.

    Can anyone shed further light on how to correct the problem?

    You can try running it under gdb, but as the project doesn't have a
    bugzilla
    page, or appear to be actively under development, you'll have to figure out how to fix it yourself.

    It may be exceeding one of the limits explained at http://ploticus.sourceforge.net/doc/limits.html

    Regards, Dave Hodgins

    Dave, thanks for the explanation and pointing me to the documentation.
    One of my data sources has been down for some days - lots of zero data
    may explain the problem.

    --
    Grimble
    Registered Linux User #450547
    Machine 'mozart' running Plasma 5.15.4 on 5.6.14-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)