Re: Version 3.37... (prg2lout crash)

Mark Summerfield <[email protected]> writes:

>> For easier debugging, I'd recommend running only `prg2lout' (with the
>> appropriate input file), as in:
>>
>>   $ valgrind prg2lout -r -lC -ilouti1 -olout1 -elout.err -t8 -T8s
>
> Grrr, if I could do that I would! But how can I when those files are
> generated by lout? (The reason the prg2lout output appeared above was
> because I build prg2lout with one of the debug flags set to 1.)

The `-i' file is the input file (`foo.c'), `-o' is output (`foo.lout'),
and `-e' is error output.  So you can try with whatever C file you have
at hand.

Hope this helps,
Ludo'.