Re: [44net] FW: JNOS2.0K and Netrom problem

Exactly along the lines of Brian's post, I recently had a report of LInpac crashing at started up on Glibc 2.24 / GCC 6.3.0 based systems (Debian 9.0/Stretch, Debian 10.0/Sid, and Arch Linux). This was really strange as this program has been working just fine call older generations of Linux distros, etc. The initial crash was always consistent but we found over four different workarounds to get it to successfully run which did not make any sense. Ultimately, it turned out that the new GCC was behaving differently on memory release operations compared to say GCC 4.9.2 (found in Debian 8.0 / Jessie). A few code changes were require to stop using the library call "delete[]" and now use "free ()" solved the issue. Definitely a pain but this is one of those "progress" pains that all software developers have to pay. As to how to better troubleshoot this Jnos issue, you need to run a gdb backtrace. I just checked Jnos 2.0K and it leaves in debugging objects by default (unnecessary actually). Once compiled, run Jnos via gdb, "run" the processand once it crashes, request a backtrace. This is a decent, non-complicated example: http://wiki.freepascal.org/Creating_a_Backtrace_with_GDB From there, take this backtrace detail to the Jnos support email list and Maiko. --David KI6ZHD