Anyway , cut a long story short, this is the fixed script, thanks to help from Alexander & Mike - sorry for misdirecting some reply emails to the list .
Primarily, an un-quoted symbol should have been quoted, and a '(list ...)' should have been a '(cons ...)' . These are the sort of problems I'd expect the picolisp debugger to help discover - ie. we should really track down what is making it coredump in the non-'+'-suffixed '(argv)' case when no error was reported when debugging is enabled by '+' argv suffix - that was my only picolisp specific complaint . Really, I am going to prioritize working for my own use on gdb debugger extension that understands the picolisp debugger and can hook into it, combined with a SIGSEGV + SIGBUS + SIGILL ... fatal signal handler that, if the fatal signal is in a picolisp code section, will inform picolisp debugger & make it print the stack & current environments & gdb back-trace to a (set of) Emacs or Vim buffer(s) if on a terminal or to a file(s) . This is really better than digging coredumps out of the systemd 'coredumpctl' compressed archive, and manually entering gdb commands to inspect picolisp memory - really, some GDB <-> picolisp integration is needed, along with a Emacs / Vi / HTML GUI for it , IMHO . Compare picolisp's debugging facilities with those of SBCL + Slime - they are a bit primitive by comparison . I really think there should eventually be a core-dumping fatal signal handler that can throw a picolisp Exception , that can be optionally installed, then this can be trapped by scripts and they could then potentially restart themselves after logging this occurence . I will work on this . Best Regards, Jason Eventually, I'd make proper '+Route+' Class objects from these idx tree IP/PFX indexed idx tree assoc lists .
L_RT.l
Description: Binary data
