[Fluxus] fluxus segfault with 4 levels of dirs in path

[Glauber Alex Dias Prado]

Dave Griffiths <dave at pawfal.org> writes:

> On Fri, 2007-09-07 at 15:47 -0300, Glauber Alex Dias Prado wrote:
>> Dave Griffiths <dave at pawfal.org> writes:
>> 
>> >> > as I had feared, something deep within mzscheme...
>> >> > I just can't reproduce it, I tried:
>> >> 
>> >> Well it isnt really a problem as it isnt strictly needed to start fluxus
>> >> from such path location, but what do you think i should do about it?
>> >
>> > not sure - is this only a problem when specifying the full path on the
>> > commandline, i.e. does it load from a path ok as normal?
>> 
>> yes it loads ok, as long as it is in the /root/first/second/third but if
>> i try in the .../fourth it brakes, not a big issue as long as it keep as
>> it is i think :).
>
> what happens if it's in 
> /root/first/second/third/forth
> which for sake of argument is in your path, and you can call just
> "fluxus" on the commandline?
>
> cheers,
>
> dave
it doesnt start segfaults i call it like this:

/home/glauber/live/fluxus/fluxus

segfault at 0x39nnn

if i call it like:

/home/glauber/live/fluxus

it is really strange the debugger session wasnt of any help?

Anyway forget about this, it is not really bothering me as i can still start
it with 3 levels of dirs, lets assume it works :), although i am curious
on why it behaves like this.

Cheers,

greb.