Re: Re: My gsoc project

Hi Frode, and thanks for the reply. I found this out today, so i
changed the source, also i changed (setf (ether-source source start
:source-start source-start) source...
to (setf (ether-source packet start :source-start source-start)
source... and don't get any more error messages.
It seems though that it gets in an infinite loop in the last assert of
ip4-init. Currently I'm trying to find out why this happens.
I would also like to ask, is there some keyboard shortcut that causes
an interrupt in movitz, like C-c C-c in slime? So I could perhaps
backtrace and find out where it gets stuck/infinite-loops (right now
my movitz mode isn't working as it should and i have to add print
lines and create-image every time).

Thanks,

Antonis


On 12 Jun 2008 14:55:15 +0200, Frode Vatvedt Fjeld
<[email protected]> wrote:
> "Antonis Antoniadis" <[email protected]> writes:
>
>  > http://www.wetsand.org:8080/pictures/screen.png <--- here I uploaded a
>  > screenshot with the error messages.
>
>
> Hi Antonis, sorry about the delay. The error means that the function
>  (setf ether-source) received bad keyword arguments (from
>  format-ethernet-packet, the backtrace says). And indeed the keywords
>  were missing in format-ethernet-packet. I've checked in a fix, but I
>  don't have time to do any testing until this evening.
>
>  Frode
>
>
>  --
>  Frode Vatvedt Fjeld
>
>  _______________________________________________
>  movitz-devel site list
>  [email protected]
>  http://common-lisp.net/mailman/listinfo/movitz-devel
>