You're trying to access unassigned memory in your examples, C would crash if
you went out of bounds on an array too. The only viable options you have in
your example are car and cdr. Hope that helped.

/Henrik

On Sat, Apr 19, 2008 at 5:56 AM, Tomas Hlavaty <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> picolisp crashes on
>
> $ ./p
> : (cadr (cons 1 2))
> Segmentation fault (core dumped)
> $
>
> both on 32 bit (picoLisp-2.3.2) and 64 bit (minipicolisp) machines.
>
> It crashes for (cadr '(1 . 2)) too.
>
> Is anybody experiencing the same bug?
>
> Is this the right place to report bugs or is there any bug tracking
> system for picolisp?
>
> Thank you,
>
> Tomas
> --
> UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
>

------=_Part_10605_29354927.1208575388400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You&#39;re trying to access unassigned memory in your examples, C would crash 
if you went out of bounds on an array too. The only viable options you have in 
your example are car and cdr. Hope that helped.<br><br>/Henrik<br>
<br><div class="gmail_quote">On Sat, Apr 19, 2008 at 5:56 AM, Tomas Hlavaty 
&lt;<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>&gt; 
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid 
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
picolisp crashes on<br>
<br>
$ ./p<br>
: (cadr (cons 1 2))<br>
Segmentation fault (core dumped)<br>
$<br>
<br>
both on 32 bit (picoLisp-2.3.2) and 64 bit (minipicolisp) machines.<br>
<br>
It crashes for (cadr &#39;(1 . 2)) too.<br>
<br>
Is anybody experiencing the same bug?<br>
<br>
Is this the right place to report bugs or is there any bug tracking<br>
system for picolisp?<br>
<br>
Thank you,<br>
<br>
Tomas<br>
<font color="#888888">--<br>
UNSUBSCRIBE: mailto:<a 
href="mailto:picolisp@software-lab.de";>picolisp@software-lab.de</a>?subject=Unsubscribe<br>
</font></blockquote></div><br>

------=_Part_10605_29354927.1208575388400--
-- 
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
-------

Reply via email to