Hi,
< Le lundi 21 décembre 2009 à 00:39:25 +0100 (CET), Taco Hoekwater écrivit :>
> That second patch I sent you privately works (tested by Norbert),
> and that will be included in metapost 1.209.
At last I tested the patch, it is working here also.
Thanks.
Jean-Paul.
--
--
Hi,
Jean-Paul Vincent wrote:
< Le dimanche 20 décembre 2009 à 11:04:33 +0100 (CET), Taco Hoekwater écrivit :>
I cannot reproduce the segfault.
-
Hardware or kernel bug? I will try 2.6.30 kernel (I am working with 2.6.31
kernel).
That
On Sun, 20 Dec 2009, Taco Hoekwater wrote:
> + va_start(ap, msg);
>(void)vfprintf(mpx->errfile, msg, ap);
> + va_end(ap);
>fprintf(mpx->errfile, "\n");
Gives:
../../../source/texk/web2c/mplibdir/mpxout.w:214: error: 'va_start' used in
function with fixed args
Best wishes
Norbert
Hi,
Jean-Paul Vincent wrote:
#1 0x004054a7 in mpx_printf (mpx=0x7581e010,
header=,
msg=0x46c1e8 "Command failed: %s; see mpxerr.log", ap=0x7fffd810)
at ../../../source/texk/web2c/mplibdir/mpxout.w:214
Ok, got it, I think. Please apply the diff below to mpxout.w
Hi,
< Le dimanche 20 décembre 2009 à 17:05:03 +0100 (CET), Taco Hoekwater écrivit :>
> If you are willing to compile from scratch, then a backtrace of a
> non-stripped metapost would be quite helpful.
>
> http://foundry.supelec.fr/gf/project/metapost/frs/
>
> This has a slightly different ver
Jean-Paul Vincent wrote:
It seems this is the same output as before.
Can I try something else?
If you are willing to compile from scratch, then a backtrace of a
non-stripped metapost would be quite helpful.
http://foundry.supelec.fr/gf/project/metapost/frs/
This has a slightly different v
< Le dimanche 20 décembre 2009 à 15:47:03 +0100 (CET), Taco Hoekwater écrivit :>
> Can you see what happens if set LC_MESSAGES in the
> environment to something like 'C'?
I export LC_MESSAGES=C and run valgrind
-
valgrind mpost logist
Jean-Paul Vincent wrote:
==19611== Address 0xffa8 is not stack'd, malloc'd or (recently)
free'd
==19611==
Hardware or kernel bug? I will try 2.6.30 kernel (I am working with 2.6.31
kernel).
With an address like that, a segfault does not surprise me in the
least ;) In cas
< 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 dete
Hi,
Norbert Preining wrote:
- mpost should not segfault on a missing etex
I cannot reproduce the segfault. The output below is from /bin/bash,
but I also tried with zsh, same results. Does debian have a private
executable, or is it reusing the texlive one?
logistic.mp is attached.
Best wish
clone 561500 -1
reassign -1 texlive-binaries
retitle -1 etex is missing
thanks
On Thu, 17 Dec 2009, Jean-Paul Vincent wrote:
> because etex is gone. The command:
Sorry, my fault. Cloning this bug (for the segfault to be checked)
and reinstantiating etex in our packages.
Best wishes
Norbert
---
On Sat, 19 Dec 2009, Karl Berry wrote:
> > because etex is gone.
>
> etex is not gone. That would be crazy. If you deleted it in Debian,
> please undelete it.
Bummer what have I done. Thanks ... I somehow lost it on the way ...
Best wishes
Norbert
---
> because etex is gone.
etex is not gone. That would be crazy. If you deleted it in Debian,
please undelete it.
- first the TEX seting in texmf.cnf should be changed,
I don't agree. As far as I can see, etex is exactly the right thing to
be using, and there is no alternative.
-
Hi Taco, hi all,
at the Debian side we got the following bug report, but it seems
that it applies to TeX Live upstream as well since the texmf.cnf
variable is present there, too:
On Thu, 17 Dec 2009, Jean-Paul Vincent wrote:
> A metapost file with: *btex etex*, inside do not compile. No problem
Package: tex-common
Version: 2.03
Severity: normal
A metapost file with: *btex etex*, inside do not compile. No problem
without btex-etex.
I found that the error is coming from the following line of texmf.cnf:
% Used by makempx to run TeX. We use "etex" because Me
15 matches
Mail list logo
