>It sure does.  Your bug is due to a broken alloca() being called from
>execl. I can't believe something as evil as alloca is still breathing.

Yup- I figured this out and punted up a question to developers
to see whether there's a reason why I shouldn't just fix this
puppy....

There's nothing wrong with alloca, per se, the problem here is that
you can't assume that your allocation stays around when you leave
the block you alloc it in. That's just plain wrong (let alone being
a formal memory leak...)...

As soon as the stupid mail queue on homeworld moves my last message
on through and we get some fine minds to respond, we'll move ahead.

Man- this flu of mine is really virulent- libc/alpha caught it....

-matt