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: Problems with SciTE 3.31 and context package
Date: Fri, 17 May 2013 20:20:14 +0200	[thread overview]
Message-ID: <519674DE.1080204@wxs.nl> (raw)
In-Reply-To: <51966BC1.9000009@meahan.net>

On 5/17/2013 7:41 PM, Bill Meahan wrote:
> Having a bit of a problem. I installed SciTE, scintillua and Hans'
> customizations yesterday and things are not working. SciTE crashes as
> soon as my context files are loaded.
>
> SciTE is version 3.31 (latest)
> scintillua is version 3.3.0-1 (latest precompiled which has 64-bit .so
> file included)
>
> context add-ons are from a recent beta and have file dates as late as
> 28-April-2013
>
> system is Linux LadyGeraldine 3.2.0-43-generic #68-Ubuntu SMP Wed May 15
> 03:33:33 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> wwm@LadyGeraldine$ SciTE
> Lua Error: /usr/share/scite/lexers/scite-context-lexer.lua:508: attempt
> to compare number with nil.
> Lua Error: Table of folds expected from 'lexer.fold'.
> Lua Error: /usr/share/scite/lexers/scite-context-lexer.lua:508: attempt

at least you see a message -) on windows they go into the void which 
makes debugging painful

> to compare number with nil.
> *** glibc detected *** SciTE: realloc(): invalid pointer: 0x09d9e5c0 ***

that one normaly points to a c bug

> Backtrace not included
>
> I'll try compiling from source if you think it will help.
>
> Ideas appreciated. Thanks

you can try to comment

lexer.fold        = context.fold

in scite-context-lexer

it looks like there has been quite some changes (i might as well wait 
till a next version before i look into it)

i replace some lua code that ships with the lexer lib; when i started 
with making the lexers i had so many crashes on big files that i made my 
own fold routine - which of course interfaces to some low lever data 
structures - to get it working; it also was much faster (the same for 
some more patched code)

then, a few versions back the low level folder (c code) changed an di 
adapted to that (as we lack access to scite properties i cannot check 
versions) and now i need to check again

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
___________________________________________________________________________________


  parent reply	other threads:[~2013-05-17 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 17:41 Bill Meahan
2013-05-17 17:52 ` Hans Hagen
2013-05-17 18:20 ` Hans Hagen [this message]
2013-05-17 18:34   ` Bill Meahan

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=519674DE.1080204@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).