Segmentation Fault in guile-1.8.7 on recent Macbook Pro

Segmentation Fault in guile-1.8.7 on recent Macbook Pro

[Fabian Schuetz]

While experimenting with "undefine", I discovered, that 
even quite important functions, like "write" or "display"
can be undefined. The problem is, that calling them
after they have been "undefined", leads to an 
endless regression, displaying a Segmentation fault,
when finally interrupted. 

If I "undefine" list:
(undefine list)
and call it afterwards:
(list 1 2 3 4)
I get the expected "ABORT: (unbound-variable)

I would be glad to help out, to fix this.

Be greeted,
Fabian Schütz

Re: Segmentation Fault in guile-1.8.7 on recent Macbook Pro

[Neil Jerram]

Fabian Schuetz <info@fms-edv.de> writes:

> While experimenting with "undefine", I discovered, that 
> even quite important functions, like "write" or "display"
> can be undefined. The problem is, that calling them
> after they have been "undefined", leads to an 
> endless regression, displaying a Segmentation fault,
> when finally interrupted. 
>
> If I "undefine" list:
> (undefine list)
> and call it afterwards:
> (list 1 2 3 4)
> I get the expected "ABORT: (unbound-variable)
>
> I would be glad to help out, to fix this.

Can you explain why you need to undefine those functions?

Unless there's a compelling need, I'm afraid it's unlikely anyone will
work on this, because most developer focus is now on 1.9/2.0.

Thanks,
        Neil

Re: Segmentation Fault in guile-1.8.7 on recent Macbook Pro

[Andy Wingo]

On Sat 30 Oct 2010 17:58, Neil Jerram <neil@ossau.uklinux.net> writes:

> Fabian Schuetz <info@fms-edv.de> writes:
>
>> (undefine list)
>
> Unless there's a compelling need, I'm afraid it's unlikely anyone will
> work on this, because most developer focus is now on 1.9/2.0.

Indeed, `undefine' doesn't exist in 1.9/2.0.

If you still have questions, Fabian, let us know how we can help you do
what you need to do without using undefine.

Andy
-- 
http://wingolog.org/