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
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 { prefsrc:192.168.
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 w
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 { pre
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.
S
> 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
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 (null-point
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
..
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
