Re: [9fans] o/mero and o/live distribution

[Alexander Sychev <santucco@gmail.com>]

Hello!

When I make the "Close" action on the main window (the upper left brown  
square), I have got an error on the host console:
[Wtree] Broken: "Segmentation violation"

I hope this stack dump helps you:

closetree(p=@89fe8b8) wtree.b:272.17, 29
         dp=nil
         i=0
treeproc(t=@89fea58) wtree.b:695.3, 16
         rp=@89fe8b8
         o=@89febb8
         op=@89febb8
         blocked=nil
         elems=nil
         onhold=nil
         op=@89febb8
         released=nil
         blkd=0
         newname=[0] ""
         p=nil
         tt=nil
         force=0
         pelems=nil
         ppath=[0] ""
         x=nil


BTW, after building from sources I have got an error:

% o/ports
% o/mero
% mkdir /mnt/ui/s0
% o/x
cannot load /dis/o/tblks.dis: link typecheck Tblks->init()  
72566fd2/10098dba

I use the 20071003 inferno package (sorry, I can't get more fresh sources  
 from svn).


On Fri, 14 Mar 2008 19:33:03 +0300, Fco. J. Ballesteros <nemo@lsub.org>  
wrote:

> Well, finally, I have been able to use this thing for a whole
> day^H^H^H testing period without seeing it crash or corrupt one of my
> files.
>
> At http://lsub.org/ls/octopus.html you may find links to omero.src.tgz
> and to omero.dis.tgz Also at /n/sources/contrib/nemo/octopus
>
> There are man pages included and a readme detailing how to run it.
> (http://lsub.org/sys/oman has the entire man for the octopus).
> olive(1) contains all the information needed to learn to use this
> weird thing, although you might need to refer to Plan 9's sam(1) or
> its tutorial regarding the command language.
>
> I wouldn't use it other than to test and try it.  It might eat your
> files.  I'll be using it instead of Plan B's omero from now on and
> it's likely that most of the bugs remaining will bite me in the near
> future.
>
> To avoid adding noise to the list, I'll be updating the distribution
> in the web and sources but I wont send further announces regarding
> this thing.
>
> BTW, this time I'm using charon's fonts and I wont believe that it
> crashes for you due to fonts (it will do for all other things,
> probably).
>
> thanks in advance for any stack dump :)



-- 
Best regards,
   santucco