Thanks for your 2 cents worth, Alex -- and for 'picolisp-json' , which
the code uses, and which is really great . Now I don't need NodeJS !
I agree, that particular code was a 1st working version horrible
"quick and dirty" coded version, a much better version is attached.
But the point of
Hi Jason,
I don't want to be rude, but to put emphasis on what Alexander Burger
wrote, your code is really bad. It doesn't follow any of the very simple
"naming conventions" of PicoLisp, and it doesn't even follow other
LISP "coding conventions". It's hard to read, difficult to grok, messy,
Hi Jason,
> 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 .
As I tried to explain several times in this thread (in this
Much better (final) version.
L_RT.l
Description: Binary data
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
Loop is now as you suggested, same problem :
(let ( ... r NIL)
...
(for r (idx ratr)
(when (and (bool r) (lst? r))
(let
( (k . v) r )
(case k
(( "dst" "gateway" "dev" "metric" ))
(T
(out 1 (prin (pack k ":" v
On Wed, Aug 02, 2023 at 09:15:54PM +0200, Alexander Burger wrote:
> On Wed, Aug 02, 2023 at 07:41:23PM +0200, Alexander Burger wrote:
> > Though I don't know the reason for the crash, pleaes
> > try to stick with pil conventions
Other issues are:
1. In 'ipv4-route-flag' there is
(let
On Wed, Aug 02, 2023 at 07:41:23PM +0200, Alexander Burger wrote:
> Though I don't know the reason for the crash, pleaes
> try to stick with pil conventions
For example, in 'load-routes' there is
(let ( cnt 0 tits NIL)
However, 'cnt' is a built-in function, which is now bound to 0
> So the code MUST be in this loop when the coredump occurs :
OK
Though I don't know the reason for the crash, pleaes
try to stick with pil conventions
>(for r (idx ratr)
(foa R (idx Ratr)
> (when (and (bool r) (lst? r))
(when (and R (lst? R))
which is
Hi Jason,
> >Can you debug this a little more? E.g. look at the output of (traceAll) and
> >see
> > *where* exactly it happens.
>
> That's the whole problem - doesn't 'traceAll' depend on Debug Mode
> being enabled by trailing '+' ?
Oh, right, you said it happens only if *not* in debug mode.
The coredump occurs within this loop of the 'prin_route' function,
for the same route, only when debug mode is enabled, as can be
proved by the output ending with '{' :
$ L_RT.l -pr
0.0.0.0/0 wlp59s0 192.168.43.1UP,GW
600 {
Good day Alex -
RE:
>Can you debug this a little more? E.g. look at the output of (traceAll) and see
> *where* exactly it happens.
That's the whole problem - doesn't 'traceAll' depend on Debug Mode
being enabled by trailing '+' ?
And the coredump does NOT occur in debug mode, nor in normal
usage
I should alsohave made more clear that on my host
it the core dump occurs when trying to print out this
pair of routes, printed by the trailing '+' debugging enabled run :
192.168.42.1/32 ppp00.0.0.0 UP,HO
0 {
Good day, Mike -
Without any arguments, it does nothing .
I did write in previous mails (I think):
$ pil L_RT.l -pr # coredumps
/ $ pil L_RT.l -pr + # no coredump
Sorry if I did not make that clear .
L_RT.l is a half-finished part of an appilication specific Web-Based
IP + VPN
Hi Mike,
> > Can you debug this a little more? E.g. look at the output of (traceAll) and
> > see
> > *where* exactly it happens.
>
> I am interested in debug this. Can i get a copy of script? I have fedora
> rawhide instance.
Great, thanks! I've sent you Jason's mails/
☺/ A!ex
--
Hi all,
> Can you debug this a little more? E.g. look at the output of (traceAll) and
> see
> *where* exactly it happens.
I am interested in debug this. Can i get a copy of script? I have fedora
rawhide instance.
(mike)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Jason,
I did not try to install and run it.
But I think it is by chance that "+" has an influence on the crash. There must
be a "hard" reason.
What I can see from the stack backtrace, it crashes in 'consTree', so it must be
in one of the 'idx' calls.
Can you debug this a little more? E.g.
17 matches
Mail list logo
