From: David Kastrup <dak@gnu.org>
Subject: Re: process output has become a bit random...
Date: 29 Jul 2004 14:49:33 +0200 [thread overview]
Message-ID: <x5acxjyo4i.fsf@lola.goethe.zz> (raw)
In-Reply-To: <ceare1$bv9$2@sea.gmane.org>
Ralf Angeli <angeli@iwi.uni-sb.de> writes:
> * David Kastrup (2004-07-29) writes:
>
> > Use circ.tex as delivered. That typically gives 1-2 problems pretty
> > often. The problem depends on the size of the file. Using really
> > large documents with hundreds of images is pretty certain to trigger
> > it.
>
> Then I get something like this in the output buffer:
>
> [...]
> Preview-LaTeX exited abnormally with code 1 at Thu Jul 29 14:41:04
> Running `Preview-DviPNG' with ``dvipng circ.dvi -o circ.prv/tmp11392cK/prev%03d.png --bd 1 -D87 ''
> Parser: End of Preview snippet 8 unexpected
> Parser: Preview snippet 17 out of sequence
> Parser: End of Preview snippet 27 unexpected
> Parser: End of Preview snippet 31 unexpected
> Parser: End of Preview snippet 48 unexpected
> Parser: Preview snippet 57 out of sequence
> Parser: Preview snippet 68 out of sequence
> Parser: Preview snippet 79 out of sequence
> Parser: Preview snippet 97 out of sequence
> Parser: Preview snippet 100 out of sequence
> [...]
> Preview-DviPNG finished at Thu Jul 29 14:41:07
> DviPNG sentinel: Wrong type argument: arrayp, nil
Yes, that's it. Even though the very last line would appear to be a
preview-latex internal bug. If you take a look at the run buffer (C-c
C-l) and search for, say, "Snippet 8", you will find that some
passages around the matches are replicated.
It is probably some change in process.c or coding.c in the last month
or so. If you use gcc-3.3.4, at least it does not seem to be
gcc-3.4-related like I feared at first.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-07-29 12:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 16:44 process output has become a bit random David Kastrup
2004-07-28 22:43 ` Peter Heslin
2004-07-28 23:40 ` Kim F. Storm
2004-07-29 6:14 ` David Kastrup
2004-07-29 8:21 ` Kim F. Storm
2004-07-29 10:29 ` Peter Heslin
2004-07-29 10:45 ` David Kastrup
2004-07-29 10:55 ` Lars Hansen
2004-07-29 11:08 ` David Kastrup
2004-07-29 12:02 ` Kim F. Storm
2004-07-29 12:12 ` David Kastrup
2004-07-29 12:26 ` Ralf Angeli
2004-07-29 12:31 ` David Kastrup
2004-07-29 12:43 ` Ralf Angeli
2004-07-29 12:49 ` David Kastrup [this message]
2004-07-29 13:05 ` Kenichi Handa
2004-07-29 13:16 ` David Kastrup
2004-07-29 14:09 ` David Kastrup
2004-07-29 14:20 ` Kim F. Storm
2004-07-29 14:57 ` David Kastrup
2004-07-29 14:58 ` Kim F. Storm
2004-07-29 20:59 ` David Kastrup
2004-08-01 0:28 ` David Kastrup
2004-08-01 23:49 ` Kim F. Storm
2004-08-02 0:03 ` Kenichi Handa
2004-08-03 1:44 ` Kenichi Handa
2004-08-03 2:07 ` David Kastrup
2004-08-03 5:20 ` Kenichi Handa
2004-08-03 10:49 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5acxjyo4i.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.