< Le dimanche 20 décembre 2009 à 11:04:33 +0100 (CET), Taco Hoekwater écrivit :>
> I cannot reproduce the segfault.
OK. I tried valgrind too. The output is different:
---------------------------------------------------------
~% valgrind mpost logistic.mp
==19611== Memcheck, a memory error detector
==19611== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==19611== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright
info
==19611== Command: mpost logistic.mp
==19611==
This is MetaPost, version 1.208 (kpathsea version 5.0.0)
(./logistic.mpfatal: exec failed: No such file or directory==19611== Invalid
read of size 1
==19611== at 0x5306451: vfprintf (vfprintf.c:1601)
==19611== by 0x405666: ??? (in /usr/bin/mpost)
==19611== by 0x406792: ??? (in /usr/bin/mpost)
==19611== by 0x409E5B: ??? (in /usr/bin/mpost)
==19611== by 0x40CA8D: ??? (in /usr/bin/mpost)
==19611== by 0x4028B0: ??? (in /usr/bin/mpost)
==19611== by 0x42F5EA: ??? (in /usr/bin/mpost)
==19611== by 0x434F77: ??? (in /usr/bin/mpost)
==19611== by 0x432E0F: ??? (in /usr/bin/mpost)
==19611== by 0x431BDC: ??? (in /usr/bin/mpost)
==19611== by 0x432947: ??? (in /usr/bin/mpost)
==19611== by 0x43CDC7: ??? (in /usr/bin/mpost)
==19611== Address 0xffffffffffffffa8 is not stack'd, malloc'd or (recently)
free'd
==19611==
==19611==
==19611== Process terminating with default action of signal 11 (SIGSEGV)
==19611== Access not within mapped region at address 0xFFFFFFFFFFFFFFA8
==19611== at 0x5306451: vfprintf (vfprintf.c:1601)
==19611== by 0x405666: ??? (in /usr/bin/mpost)
==19611== by 0x406792: ??? (in /usr/bin/mpost)
==19611== by 0x409E5B: ??? (in /usr/bin/mpost)
==19611== by 0x40CA8D: ??? (in /usr/bin/mpost)
==19611== by 0x4028B0: ??? (in /usr/bin/mpost)
==19611== by 0x42F5EA: ??? (in /usr/bin/mpost)
==19611== by 0x434F77: ??? (in /usr/bin/mpost)
==19611== by 0x432E0F: ??? (in /usr/bin/mpost)
==19611== by 0x431BDC: ??? (in /usr/bin/mpost)
==19611== by 0x432947: ??? (in /usr/bin/mpost)
==19611== by 0x43CDC7: ??? (in /usr/bin/mpost)
==19611== If you believe this happened as a result of a stack
==19611== overflow in your program's main thread (unlikely but
==19611== possible), you can try to increase the size of the
==19611== main thread stack using the --main-stacksize= flag.
==19611== The main thread stack size used in this run was 8388608.
==19611==
==19611== HEAP SUMMARY:
==19611== in use at exit: 35,690,844 bytes in 86,487 blocks
==19611== total heap usage: 137,615 allocs, 51,128 frees, 70,553,179 bytes
allocated
==19611==
==19611== LEAK SUMMARY:
==19611== definitely lost: 3,727 bytes in 210 blocks
==19611== indirectly lost: 1,206 bytes in 80 blocks
==19611== possibly lost: 0 bytes in 0 blocks
==19611== still reachable: 35,685,911 bytes in 86,197 blocks
==19611== suppressed: 0 bytes in 0 blocks
==19611== Rerun with --leak-check=full to see details of leaked memory
==19611==
==19611== For counts of detected and suppressed errors, rerun with: -v
==19611== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
fatal: Command failed: etex --parse-first-line --interaction=nonstopmode
mp315810.tex; see mpxerr.log
>> logistic2.mp
>> logistic2.mpx
! Unable to make mpx file.
l.35 label.bot(btex
$r$ etex, ((rmax-0.2)*ux,0));
Transcript written on logistic.log.
==19611==
==19611== HEAP SUMMARY:
==19611== in use at exit: 1,996,908 bytes in 86,327 blocks
==19611== total heap usage: 137,665 allocs, 51,338 frees, 70,586,158 bytes
allocated
==19611==
==19611== LEAK SUMMARY:
==19611== definitely lost: 3,805 bytes in 212 blocks
==19611== indirectly lost: 1,206 bytes in 80 blocks
==19611== possibly lost: 0 bytes in 0 blocks
==19611== still reachable: 1,991,897 bytes in 86,035 blocks
==19611== suppressed: 0 bytes in 0 blocks
==19611== Rerun with --leak-check=full to see details of leaked memory
==19611==
==19611== For counts of detected and suppressed errors, rerun with: -v
==19611== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
------------------------------------------------------------------------
Hardware or kernel bug? I will try 2.6.30 kernel (I am working with 2.6.31
kernel).
Regards.
Jean-Paul Vincent.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
