------art_10913_10096338.1127634595532
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thank you _why
tarball now included, comment below

>> Narrowing the problem a little, here is some code that does not segfault:
>>
>> http://www.jus.uio.no/sisu/debug/
>> it contains a (newer) version of the code for sisu
>> with use of yaml commented out.
>>
>> to cause segfault, uncomment line 56 (require 'yaml') in file:
>> lib/sisu/0.26/sysenv.rb
>>
>> segfault also occurs if
>> require 'yaml' is moved earlier in processing
>> e.g. to bin/sisu
>> and occurs on require 'yaml' regardless of whether yaml
>> is acutally used for anything.
>>
>> segfault has been repeated on multiple installs of ruby
>> (same version) and more than one machine.
>>

Sorry i did not include a tarball, earlier, tarball added as
http://www.jus.uio.no/sisu/debug/debug_sisu_ruby_1.8.3_20050921_segfaultless_test_case.tgz
http://www.jus.uio.no/sisu/debug/BUGREPORT

Ralph

On 9/25/05, why the lucky stiff <ruby-core / whytheluckystiff.net> wrote:
>
> Ralph Amissah wrote:
>
> >SiSU is written in Ruby. There are no extensions,
> >though external applications are used when their
> >functionality is needed, and for these it needs a
> >Unix/Gnu/Linux environment.
> >YAML is used to get optional user configuration and sisu version.
> >
> >
> Thankyou, Ralph. I'm sifting through it.
>
> Can anyone else tell me if YAML is segfaulting on their Debian boxes?
>
> _why
>
>
--
email: ralph / amissah.com
.: ralph.amissah / gmail.com
SiSU: http://www.jus.uio.no/sisu

------art_10913_10096338.1127634595532--