ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matthijs Kooijman <matthijs@stdin.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: obscure luatex error
Date: Thu, 15 Oct 2009 16:09:44 +0200	[thread overview]
Message-ID: <20091015140944.GL29762@katherina.student.utwente.nl> (raw)
In-Reply-To: <200910151556.52242.alan.braslau@cea.fr>


[-- Attachment #1.1: Type: text/plain, Size: 1863 bytes --]

Hi,

> luatex: ../../../source/texk/web2c/luatexdir/tex/printing.c:266: print: 
> Assertion `c < 256' failed.
> [329.327MTXrun | fatal error, no return code, message: luatex: execution 
> interrupted

A quick glance at the code, shows it's in the following part:

  /*
  An entire string is output by calling |print|. Note that if we are outputting
  the single standard ASCII character \.c, we could call |print("c")|, since
  |"c"=99| is the number of a single-character string, as explained above. But
  |print_char("c")| is quicker, so \TeX\ goes directly to the |print_char|
  routine when it knows that this is safe. (The present implementation
  assumes that it is always safe to print a visible ASCII character.)
  @^system dependencies@>

  The first 256 entries above the 17th unicode plane are used for a
  special trick: when \TeX\ has to print items in that range, it will
  instead print the character that results from substracting 0x110000
  from that value. This allows byte-oriented output to things like
  \.{\\specials} and \.{\\pdfliterals}. Todo: Perhaps it would be useful
  to do the same substraction while typesetting.
  */

  void print(integer s)
  {                               /* prints string |s| */
  ...
              } else if (s >= 0x110000) {
                  int c = s - 0x110000;
                  assert(c < 256);
                  print_char(c);
              } else {
  ...
  }

It seems the second comment block talks about the code in which the error
occurs. It also seems that this is either caused by some very high unicode
character that's printed, or some invalid (uninitialized?) value is passed to
print().

Do you think you could compile luatex with CFLAGS=-g, and run it in gdb to get
a backtrace? That might help to see where this comes from...

Gr.

Matthijs

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-10-15 14:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 19:37 virtual fonts in luatex? Thomas A. Schmitz
2009-10-01  7:48 ` Taco Hoekwater
2009-10-01  8:22   ` Thomas A. Schmitz
2009-10-01 17:55   ` Hans Hagen
2009-10-01 18:18     ` Thomas A. Schmitz
2009-10-01 18:23       ` Hans Hagen
2009-10-15 13:56         ` obscure luatex error Alan BRASLAU
2009-10-15 14:09           ` Matthijs Kooijman [this message]
2009-10-15 14:18             ` Taco Hoekwater
2009-10-15 14:27             ` luigi scarso
2009-10-15 14:28               ` Taco Hoekwater
2009-10-15 14:32               ` Matthijs Kooijman
2009-10-15 14:36                 ` luigi scarso
2009-10-15 15:08                   ` Alan BRASLAU
2009-10-15 15:13                     ` luigi scarso
     [not found] ` <200910160955.19746.alan.braslau@cea.fr>
     [not found]   ` <4AD86411.6040005@elvenkind.com>
2009-10-17 11:50     ` obscure luatex error (fixed!) Alan BRASLAU
2009-10-17 12:02       ` Mojca Miklavec

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=20091015140944.GL29762@katherina.student.utwente.nl \
    --to=matthijs@stdin.nl \
    --cc=ntg-context@ntg.nl \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).