1. Forum
  2. FidoNet
  3. BINKD

  • Sigint 11

    From Kees van Eeten@2:280/5003.4 to All on Sunday, January 10, 2016 17:08:42
    Hello Binkd developers,

    When I run binkd/1.1a-75/Linux in the amd64 or Intel32
    version, sessions end with:

    08 Jan 22:07:13 [11923] process 11924 exited by signal 11

    As far as I know that is an adressing error, for addresses outside
    the memory space.

    The same software on ARM/32-Linux works perfectly well.

    Al executables are compiled locally from the same sources downloaded from
    cvs.happy.kiev.ua

    Looking at my logs it seems that OS/2 systems are using version 1.1a-75/OS2
    so the problem seems to be at least "Intel-Linux" specific.

    Do others have the same issues?

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Wilfred van Velzen@2:280/464.112 to Kees van Eeten on Thursday, January 14, 2016 13:31:21
    Hi Kees,

    On 10 Jan 16 17:08, Kees van Eeten wrote to All:
    about: "Sigint 11":

    When I run binkd/1.1a-75/Linux in the amd64 or Intel32 version,
    sessions end with:

    08 Jan 22:07:13 [11923] process 11924 exited by signal 11

    As far as I know that is an adressing error, for addresses outside
    the memory space.

    The same software on ARM/32-Linux works perfectly well.

    Al executables are compiled locally from the same sources downloaded
    from cvs.happy.kiev.ua

    Looking at my logs it seems that OS/2 systems are using version 1.1a-75/OS2 so the problem seems to be at least "Intel-Linux"
    specific.

    Do others have the same issues?

    I'm on 72, and have no problems.

    Only perlhooks had noteworthy changes since 72, so if you don't use them, try compiling without them. If you do use them revert perlhooks.c back to a previous version and try with those...

    Wilfred.

    --- FMail-W32-1.69.10.141-B20151003
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464 to Kees van Eeten on Friday, January 15, 2016 18:20:23
    Hi,

    On 2016-01-14 13:31:21, Wilfred van Velzen wrote to Kees van Eeten:
    about: "Re: Sigint 11":

    Do others have the same issues?

    I'm on 72, and have no problems.

    I've now build 75 and it seems to be working. But I don't build with perlhooks ...

    Only perlhooks had noteworthy changes since 72, so if you don't use
    them, try compiling without them. If you do use them revert
    perlhooks.c back to a previous version and try with those...


    Bye, Wilfred.


    --- FMail-W32-1.69.12.144-B20160109
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Kees van Eeten@2:280/5003.4 to Wilfred van Velzen on Friday, January 15, 2016 18:33:56
    Hello Wilfred!

    15 Jan 16 18:20, you wrote to me:

    On 2016-01-14 13:31:21, Wilfred van Velzen wrote to Kees van Eeten:
    about: "Re: Sigint 11":

    Do others have the same issues?

    I'm on 72, and have no problems.

    I am on 73 with no problems.

    I've now build 75 and it seems to be working. But I don't build with perlhooks ...

    Only perlhooks had noteworthy changes since 72, so if you don't use
    them, try compiling without them. If you do use them revert
    perlhooks.c back to a previous version and try with those...

    That would be a way to sort this out. It appears, that the 75 version I use
    successfully on the RaspberryPi, also lacks the perlhooks.


    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)