ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: bizarre error message
Date: Sat, 29 Mar 2014 23:26:53 +0100	[thread overview]
Message-ID: <533748AD.5020504@wxs.nl> (raw)
In-Reply-To: <5336E09F.9030202@uni-bonn.de>

On 3/29/2014 4:02 PM, Thomas A. Schmitz wrote:
> Hi,
>
> I haven't yet been able to reproduce this in a minimal example, but I'm
> trying to place some images within a mixedcolumns environment, and I get
> an error message I have never seen before:
>
> pages           > flushing realpage 5, userpage 5
> Node 1150 has an attribute list that is free already
> Node 1406 has an attribute list that is free already
> Node 1373 has an attribute list that is free already
> Node 1228 has an attribute list that is free already
> Node 1195 has an attribute list that is free already
> Node 1114 has an attribute list that is free already
> Node 1127 has an attribute list that is free already
> Node 1074 has an attribute list that is free already
> Node 2011 has an attribute list that is free already
> Node 2268 has an attribute list that is free already
> Node 2116 has an attribute list that is free already
> Node 2030 has an attribute list that is free already
> Node 1981 has an attribute list that is free already
> Node 1953 has an attribute list that is free already
> Node 3055 has an attribute list that is free already
> Node 2889 has an attribute list that is free already
> luatex: ../../../source/texk/web2c/luatexdir/tex/texnodes.w:1985:
> delete_attribute_ref: Assertion
> `varmem[(b)].hh.u.B0==attribute_list_node' failed.
>
> mtx-context     | fatal error: no return code, message: luatex:
> execution interrupted%
>
> This is with context 2014.03.28 15:04 and luatex 0.78.2 on linux 64-bit.
> The error does not appear with a beta version from january 2014. Any
> idea where this might come from?

Ok, we need indeed some example of this so that we can test. It can for 
instance relate to some prev pointer still not being ok (which can 
result in such errors). This means that when context looks back at some 
node that happens to be a head node, we can get weird effects. In due 
time this will be sorted out but the more tests we have the sooner.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2014-03-29 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 15:02 Thomas A. Schmitz
2014-03-29 22:26 ` Hans Hagen [this message]
2014-04-01  9:18   ` Thomas A. Schmitz
2014-04-01  9:29     ` Hans Hagen
2014-04-01  9:46       ` Thomas A. Schmitz

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=533748AD.5020504@wxs.nl \
    --to=pragma@wxs.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).