Other note to self: don't send in bug reports when you've been up for 24 hours, it's probably your fault, anyway.
Ok. got a cvs udpate, did a make distclean, rebuilt (btw, the manifest is broken. I'm pretty sure this, at least, is not my fault. =-)...
Bother. In attempting to duplicate the problem, I see that my problem is... me. Well, and a stupid makefile rule. I used "make exit" to run the normal version and "make exit-t" to run the -t version... but I didn't strip off the -t on the file name, so instead of trying to process "exit.tcl", it was trying to process "exit-t.tcl". So the version that didn't generate any output was actually behaving nicely - there was no input file, so it stopped early. All the other versions suggested i ran by hand, avoiding my make stupidity.
<ren>Stiiiimpy, you eeeeediot!</ren>
The cvs-latest makes this *much* clearer by throwing a bus error when I try to read the file with the wrong name. (but it does that with or without the -t option.)
I apologize to all for the wild goose chase. Hopefully I'll have something to show for it shortly.
On Monday, September 22, 2003, at 08:03 AM, Leopold Toetsch wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:--Will Coleda <[EMAIL PROTECTED]> wrote:
Should "parrot -t 2> /dev/null" work the same as "parrot 2> /dev/null"
Actually it doesn't leak memory but it exhausts memory. I'm currently investigating the problem, which is caused by all the DOD/GC blocking mainly in Parrot_vsprintf ...
Please cvs update and check again if the problem still persists.
leo
Will "Coke" Coleda will at coleda dot com
