18 Mar
2017
18 Mar
'17
7:18 a.m.
Regrettably, I don't have a way to test JNOS here, so this is just
a guess:
A faint possibility is that there is something in the latest version of
the source code that is tripping a bug in the compiler. This is not
very likely, but one thing I have found helpful in debugging programs
that are acting mysteriously is to change optimization when compiling.
If the Makefile sets the CFLAGS to -O, try -O0 instead.
This can also help if you are running the program under GDB in that it
can make the fault a little easier to track down.
Best wishes
- Brian
On Sat, Mar 18, 2017 at 08:06:57PM +1100, vk1kw wrote:
More to the saga of my JNOS2.0K netrom problems here.