[nos-bbs] Jnos2.0m.1rc crash

[M Langelaar]

You mean jnos.0j.7x ?? As in from 2016 ?

Lots of bugs and stuff fixed since then. You should be using the latest 
2.0m

Maiko

On 16/02/2020 9:49 a.m., jerome schatten wrote:

> Hi Maiko, et al.
>
> Anything else that should be commented out in config.h that makes jnos wobbly?  I’m fighting a situation here, where jnos crashes out to the OS on the pi five or six times before it starts successfully and then crashes out after a number of days.  Here this has been happening on pi2b — running Stretch - and also Buster on a pi3b - no tnc’s. jnos2.07.
>
> jerome-ve7ass
>
> p.s. Thanks to all that responded to my previous questions about compiling jnos on a Buster system! I’m about to do the compile on the latest stable version of jnos to see if it changes the situation described above.
> j.
>
>   
>
>> On Feb 15, 2020, at 21:01, M Langelaar <maiko at pcsinternet.ca> wrote:
>>
>> I am guessing you have #define INP2011 in your config.h ...
>>
>> comment it out, remove it, or #undef INP2011, then :
>>
>> make clean
>>
>> ./configure
>>
>> make
>>
>> Maiko
>>
>> On 15/02/2020 10:54 p.m., Niels Ruiter wrote:
>>> My Jnos2.0m.1rc goes down every 10 to 15 hours. I use systemd so jnos will
>>> be online again fairly quickly. I can't find anything in the log files why
>>> it goes down. I have run gdb debugger and de backtrace give me this info.
>>> Jnos is running on a RPI 2b with raspbian Stretch and direwolf as software
>>> tnc
>>>
>>> (gdb) bt
>>> #0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
>>> #1  0x76c73824 in __GI_abort () at abort.c:89
>>> #2  0x76cacf78 in __libc_message (do_abort=do_abort at entry=2, fmt=<optimized
>>> out>) at ../sysdeps/posix/libc_fatal.c:175
>>> #3  0x76cb3ad4 in malloc_printerr (action=<optimized out>, str=0x76d663dc
>>> "double free or corruption (!prev)", ptr=<optimized out>,
>>>      ar_ptr=<optimized out>) at malloc.c:5049
>>> #4  0x76cb4514 in _int_free (av=0x76d82794 <main_arena>, p=0x164b08,
>>> have_lock=<optimized out>) at malloc.c:3905
>>> #5  0x0009ee38 in j_free (p=0x164b10) at unix.c:286
>>> #6  0x0009aa40 in free_n4circ (cb=0x164b10) at nr4subr.c:99
>>> #7  0x0009a6ac in nr4state (cb=0x164b10, newstate=0) at nr4.c:768
>>> #8  0x00098a58 in reset_nr4 (cb=0x164b10) at nr4user.c:217
>>> #9  0x0009d8f8 in nrresetlinks (rp=0x1695f8) at nr3.c:1419
>>> #10 0x00096a04 in doobsotick () at nrcmd.c:1277
>>> #11 0x0006ba2c in timerproc (i=0, v1=0x0, v2=0x0) at timer.c:59
>>> #12 0x000705dc in _kicker (func=0x6b95c <timerproc>, iarg=0, parg1=0x0,
>>> parg2=0x0) at ksubr.c:142
>>> #13 0x76c80830 in setcontext () at
>>> ../sysdeps/unix/sysv/linux/arm/setcontext.S:94
>>> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>>> (gdb)
>>> Program terminated with signal SIGABRT, Aborted.
>>> The program no longer exists.
>>> (gdb) quit
>>>
>>> Maybe there is someone who understands what's going on here.
>>>
>>> Thank you...
>>>
>>> 73 Niels PD9Q
>>>
>>>
>>> _______________________________________________
>>> nos-bbs mailing list
>>> nos-bbs at lists.tapr.org
>>> http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at lists.tapr.org
>> http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org