[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Version 3.37... (prg2lout crash)
From: |
Mark Summerfield |
Subject: |
Re: Version 3.37... (prg2lout crash) |
Date: |
Wed, 24 Sep 2008 13:56:39 +0100 |
User-agent: |
KMail/1.9.9 |
On 2008-09-24, Ludovic Courtès wrote:
> Mark Summerfield <address@hidden> writes:
> > I've also tried running in valgrind as per Ludovic's suggestion. The
> > crash occurs exactly as before with valgrind reporting 0 errors:
> >
> >
> > $ lout -r beginning run 5:
> > lout file "gra_tick" (from "gra" line 38, from "all" line 46):
> > 234,1: 23.7c object too high for 23.7c space; @Scale inserted
> > lout file "gra_summ" (from "gra" line 44, from "all" line 46):
> > 10,1: 25.7c object too high for 23.6c space; @Scale inserted
> > lout file "prg_embe" (from "prg" line 136, from "all" line 48):
> > 38,17: fatal error: failure (non-zero status) of filter:
> > prg2lout -r -lC -ilouti1 -olout1 -elout.err
> > -t8 -T8s ==6261==
> > ==6261== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1)
> > ==6261== malloc/free: in use at exit: 403,578,783 bytes in 99,368 blocks.
> > ==6261== malloc/free: 353,380 allocs, 254,012 frees, 1,410,357,058 bytes
> > allocated.
> > ==6261== For counts of detected errors, rerun with: -v
> > ==6261== searching for pointers to 99,368 not-freed blocks.
>
> What is it that's running under Valgrind? Only `prg2lout'? If so, did
> you modify Lout's `prg' to run "valgrind prg2lout" instead of
> "prg2lout"?
The command line I used was:
$ valgrind lout -r6 all > guide.ps
> 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.)
> > I killed it at this point.
>
> Which process did you kill? Why did you have to kill it?
I killed valgrind because my Kubuntu machine only have 500MB RAM and it
was grinding to a halt---I had to kill it from a different machine.
--
Mark Summerfield, Qtrac Ltd, www.qtrac.eu
C++, Python, Qt, PyQt - training and consultancy
"Rapid GUI Programming with Python and Qt" - ISBN 0132354187
- Re: Version 3.37... (@IncludeGraphic problem), Martti Haukijärvi, 2008/09/23
- Re: Version 3.37... (@IncludeGraphic problem), Jeff Kingston, 2008/09/23
- Re: Version 3.37... (@IncludeGraphic problem), Ludovic Courtès, 2008/09/24
- Version 3.37... (prg2lout crash), Mark Summerfield, 2008/09/24
- Re: Version 3.37... (prg2lout crash), Ludovic Courtès, 2008/09/24
- Re: Version 3.37... (prg2lout crash), J.H.M. Dassen (Ray), 2008/09/24
- Re: Version 3.37... (prg2lout crash), Mark Summerfield, 2008/09/24
- Re: Version 3.37... (prg2lout crash), Ludovic Courtès, 2008/09/24
- Re: Version 3.37... (prg2lout crash),
Mark Summerfield <=
- Re: Version 3.37... (prg2lout crash), Ludovic Courtès, 2008/09/24
- Re: Version 3.37... (prg2lout crash), Mark Summerfield, 2008/09/24
- Re: Version 3.37... (prg2lout crash), Albert Kinderman, 2008/09/24