Smarteiffel is marked broken but is not (maybe!)

Patrick Lamaiziere patfbsdp at
Sat Oct 20 06:07:27 PDT 2007

Le Wed, 17 Oct 2007 01:06:45 +0200,
Kris Kennaway <kris at> :


> > I compiled the install program with full assertions and it crashs
> > with a run-time stack dump. Looking the code it seems related to the
> > memory management by SmartEiffel (it is not good because there is a
> > garbage collector). So may be it is broken.

I was wrong, this is because a stupid bug when assertions are on. I'm
the first one who tried it with full assertions ON...

> > I will check it with FreeBSD 6.2 and another C compiler and try to
> > get more informations.
> Try building it "normally" but with MALLOC_OPTIONS=AJ.  This is
> enabled for port builds (and by default in CURRENT) and sometimes
> catches application bugs.

No it does not change anything.

I don't know why it failed on the tinderbox and i can't reproduce this
problem. SmartEiffel is marked broken since july, can it
be only a temporary problem during the evolution of CURRENT ?


More information about the freebsd-ports mailing list