From: Ralph Amissah Date: 2005-09-27T03:51:32+09:00 Subject: ruby 1.8.3 (2005-06-23) [i486-linux] sisu segfault ------=_Part_1915_29238400.1127760687180 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline http://www.jus.uio.no/sisu/SiSU/download#development http://www.jus.uio.no/sisu/SiSU/changelog#0.27 http://www.jus.uio.no/sisu/SiSU/download#dev_debian http://www.jus.uio.no/sisu/SiSU/download#debug http://www.jus.uio.no/sisu/SiSU/download#deb_debug This is a build that does not segfault with ruby 1.8.3 (2005-06-23) [i486-linux] achieved by not using yaml sisu appears to be the only application affected? The bug is low level be with ruby, and require 'yaml' line number 56 in sysenv.rb causes segfault even if nothing is done, (guess i need to triple check this, and there certainly may be some old formatting in yaml used, but by my current reckoning i am not loading the files [before the segfault]) am told actually that it is not directly related to syck/yaml (but that one line does make the difference). i have not played yet with gdb (guess i rather would not have to, and ruby is the chosen language not C) Would rather not have to engineer yaml out of sisu... and certainly would rather that ruby did not segfault. A bit frustrated, (debuging C segfaults while looking only at code written in ruby is like feeling your way in the dark). Do i file bug reports against ruby and sisu on Debian? (have no bugs reported but a couple of complaints :-( An otherwise happy ruby user. Ralph PS thx why_ Ari mfp -- email: ralph@amissah.com .: ralph.amissah@gmail.com SiSU: http://www.jus.uio.no/sisu ------=_Part_1915_29238400.1127760687180--