Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Hans Hagen

On 9/11/2019 11:02 AM, Vladimir Lomov wrote:


  │   ├── cont-en.lui
  │   └── cont-en.luv


these are regular lua files


The last two, Ok.


Indeed. These are startup related files.


That make sense, lua, (lub), luc, lud but even lua files are different
or do you mean that luc/lud are generated (compiled) from lua and then
contex don't read them only luc/lud?
The lua files are probably not that different but indeed the other ones 
are bytecode files and normally read (with the lua files as fallbacks in 
case of a failure) which is more efficient (a =lua, c = luatex bytecode 
(5.3), b = luajit bytecode (hybrid 5.1 / 5.2), d = luametatex bytecode 
(5.4). At some point the jit variant might be dropped and in the long 
run we might only have luametatex.


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Vladimir Lomov
Hello
** Hans Hagen [2019-09-11 10:54:41 +0200]:

> On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
> 
>> LUAMETATEX:
>> 
>> -- 8< 
>> --
>> tree $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
>> lmtx/
>> └── luatex-cache
>>  └── context
>>  └── 5fe67e0bfe781ce0dde776fb1556f32e
>>  ├── formats
>>  │   └── luametatex
>>  │   ├── cont-en.fmt
>>  │   ├── cont-en.log
>>  │   ├── cont-en.lui
>>  │   └── cont-en.luv
> 
> these are regular lua files

The last two, Ok.

> 
>>  └── trees
>>  ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.lua
>>  ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.luc
>>  ├── 3f406286dc3075cdfb044f836920f46a.lua
>>  ├── 3f406286dc3075cdfb044f836920f46a.luc
>>  ├── 3f6978edf9feb817ad6c1f21fc262031.lua
>>  ├── 3f6978edf9feb817ad6c1f21fc262031.luc
>>  ├── 71c82419867f9a0df8a150196c03c86f.lua
>>  ├── 71c82419867f9a0df8a150196c03c86f.luc
>>  ├── 73630a261795d9c53610a28af4550cbc.lua
>>  ├── 73630a261795d9c53610a28af4550cbc.luc
>>  ├── dcb651482955ac31eaab7723b70e0184.lua
>>  ├── dcb651482955ac31eaab7723b70e0184.luc
>>  ├── fb39a92c95ceca857c3f2d0ee48a2ad3.lua
>>  └── fb39a92c95ceca857c3f2d0ee48a2ad3.luc
> actually these *.luc files should be *.lud files so I need to check that

That make sense, lua, (lub), luc, lud but even lua files are different
or do you mean that luc/lud are generated (compiled) from lua and then
contex don't read them only luc/lud?

> 
> Hans
> 
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -

---
WBR, Vladimir Lomov

-- 
Besides, REAL computers have a rename() system call.:-)
-- Larry Wall in <7...@jpl-devvax.jpl.nasa.gov>


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Hans Hagen

On 9/11/2019 10:14 AM, Vladimir Lomov wrote:


LUAMETATEX:

-- 8< --
tree $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
lmtx/
└── luatex-cache
 └── context
 └── 5fe67e0bfe781ce0dde776fb1556f32e
 ├── formats
 │   └── luametatex
 │   ├── cont-en.fmt
 │   ├── cont-en.log
 │   ├── cont-en.lui
 │   └── cont-en.luv


these are regular lua files


 └── trees
 ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.lua
 ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.luc
 ├── 3f406286dc3075cdfb044f836920f46a.lua
 ├── 3f406286dc3075cdfb044f836920f46a.luc
 ├── 3f6978edf9feb817ad6c1f21fc262031.lua
 ├── 3f6978edf9feb817ad6c1f21fc262031.luc
 ├── 71c82419867f9a0df8a150196c03c86f.lua
 ├── 71c82419867f9a0df8a150196c03c86f.luc
 ├── 73630a261795d9c53610a28af4550cbc.lua
 ├── 73630a261795d9c53610a28af4550cbc.luc
 ├── dcb651482955ac31eaab7723b70e0184.lua
 ├── dcb651482955ac31eaab7723b70e0184.luc
 ├── fb39a92c95ceca857c3f2d0ee48a2ad3.lua
 └── fb39a92c95ceca857c3f2d0ee48a2ad3.luc

actually these *.luc files should be *.lud files so I need to check that

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Vladimir Lomov
Hello,
** Hans Hagen [2019-09-11 10:38:21 +0200]:

> On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
> 
>> so I'm sure that this is different "context"s (I'm curious why current
>> version of mkiv files are different but I suppose it is related to other
>> "system" files of context).
> 
> the lmtx files can have different solutions because luametatex has some
> possibilities that luatex hasn't (yet or never will have)

Got it.

>> Is it "safe" to simply run always
>> 
>>$ mtxrun --generate; context --make
>> 
>> after each context/lmtx update? May be one should add there commands in
>> 'install.sh'?
> 
> normally this will happen automatically but there are rare cases when it
> might fail, for instance in lmtx because there is a change in bytecode that
> gets unnoticed (we use the still experimental lua 5.4 there)

Got it, so as lmtx has "experimental" status, one should pay more
attention, be prepared to run manually 'mtxrun --generate ; context
--make', ok with me.

Thank you Hans for clarification.

> Hans
> 
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -

---
WBR, Vladimir Lomov

-- 
Subject to change without notice.


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Hans Hagen

On 9/11/2019 10:14 AM, Vladimir Lomov wrote:


so I'm sure that this is different "context"s (I'm curious why current
version of mkiv files are different but I suppose it is related to other
"system" files of context).


the lmtx files can have different solutions because luametatex has some 
possibilities that luatex hasn't (yet or never will have)



Is it "safe" to simply run always

   $ mtxrun --generate; context --make

after each context/lmtx update? May be one should add there commands in
'install.sh'?


normally this will happen automatically but there are rare cases when it 
might fail, for instance in lmtx because there is a change in bytecode 
that gets unnoticed (we use the still experimental lua 5.4 there)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Vladimir Lomov
Hello,
** Hans Hagen [2019-09-11 08:39:03 +0200]:

>
>> but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I
>> set it to $HOME/.cache/context-suite).
>
>>> I'm receiving the super helpful error message:
>>>
>>>  ! error (lua): function call: no
>>>
>>> Maybe some sort of cache versioning is in order to at least give a better 
>>> error.
>>
>> It didn't occured to me that the problem may be with the cache, it would
>> be helpfull if context/luametatex will give error message, something
>> like "cache version mismatch" and exit.

> hm, i have the same cache for both (different files are used)

That's strange. AFAIR, I splitted the caches because they were different
and I checked this again: I deleted TEXMFCACHE directories (lmtx and
context-suite ones), regenerated both using

  $ mtxrun --generate; context --make

(using the right mtxrun,
/usr/local/opt/context/tex/texmf-linux-64/bin/mtxrun and
/usr/local/opt/lmtx/tex/texmf-linux-64/bin/mtxrun in my case) and
checked the generated files. They have identical names, for example,

CONTEXT SUITE:

-- 8< --
$ tree $TEXMFCACHE | sed -e "s@$HOME/.cache/@@"
context-suite
└── luatex-cache
└── context
└── 5fe67e0bfe781ce0dde776fb1556f32e
├── formats
│   └── luatex
│   ├── cont-en.fmt
│   ├── cont-en.log
│   ├── cont-en.lui
│   └── cont-en.luv
└── trees
├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.lua
├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.luc
├── 3f406286dc3075cdfb044f836920f46a.lua
├── 3f406286dc3075cdfb044f836920f46a.luc
├── 3f6978edf9feb817ad6c1f21fc262031.lua
├── 3f6978edf9feb817ad6c1f21fc262031.luc
├── 71c82419867f9a0df8a150196c03c86f.lua
├── 71c82419867f9a0df8a150196c03c86f.luc
├── 73630a261795d9c53610a28af4550cbc.lua
├── 73630a261795d9c53610a28af4550cbc.luc
├── dcb651482955ac31eaab7723b70e0184.lua
├── dcb651482955ac31eaab7723b70e0184.luc
├── fb39a92c95ceca857c3f2d0ee48a2ad3.lua
└── fb39a92c95ceca857c3f2d0ee48a2ad3.luc

6 directories, 18 files
-- 8< --


-- 8< --
LANG=en_US.UTF-8 ls -goR $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
context-suite/:
total 0
drwxr-xr-x 3 21 Sep 11 15:28 luatex-cache

context-suite/luatex-cache:
total 0
drwxr-xr-x 3 46 Sep 11 15:28 context

context-suite/luatex-cache/context:
total 0
drwxr-xr-x 4 34 Sep 11 15:28 5fe67e0bfe781ce0dde776fb1556f32e

context-suite/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e:
total 4
drwxr-xr-x 3   20 Sep 11 15:28 formats
drwxr-xr-x 2 4096 Sep 11 15:28 trees

context-suite/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats:
total 0
drwxr-xr-x 2 82 Sep 11 15:28 luatex

context-suite/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex:
total 11044
-rw-r--r-- 1 10878224 Sep 11 15:28 cont-en.fmt
-rw-r--r-- 1   414753 Sep 11 15:28 cont-en.log
-rw-r--r-- 1 4118 Sep 11 15:28 cont-en.lui
-rw-r--r-- 1  263 Sep 11 15:28 cont-en.luv

context-suite/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/trees:
total 752
-rw-r--r-- 1  78031 Sep 11 15:28 3952aa25b6a1b9f9f8d3eeb6e65f0039.lua
-rw-r--r-- 1  45351 Sep 11 15:28 3952aa25b6a1b9f9f8d3eeb6e65f0039.luc
-rw-r--r-- 1403 Sep 11 15:28 3f406286dc3075cdfb044f836920f46a.lua
-rw-r--r-- 1398 Sep 11 15:28 3f406286dc3075cdfb044f836920f46a.luc
-rw-r--r-- 1   2026 Sep 11 15:28 3f6978edf9feb817ad6c1f21fc262031.lua
-rw-r--r-- 1   1371 Sep 11 15:28 3f6978edf9feb817ad6c1f21fc262031.luc
-rw-r--r-- 1407 Sep 11 15:28 71c82419867f9a0df8a150196c03c86f.lua
-rw-r--r-- 1400 Sep 11 15:28 71c82419867f9a0df8a150196c03c86f.luc
-rw-r--r-- 1403 Sep 11 15:28 73630a261795d9c53610a28af4550cbc.lua
-rw-r--r-- 1398 Sep 11 15:28 73630a261795d9c53610a28af4550cbc.luc
-rw-r--r-- 1 164062 Sep 11 15:28 dcb651482955ac31eaab7723b70e0184.lua
-rw-r--r-- 1  86572 Sep 11 15:28 dcb651482955ac31eaab7723b70e0184.luc
-rw-r--r-- 1 225577 Sep 11 15:28 fb39a92c95ceca857c3f2d0ee48a2ad3.lua
-rw-r--r-- 1 117644 Sep 11 15:28 fb39a92c95ceca857c3f2d0ee48a2ad3.luc
-- 8< --

###

LUAMETATEX:

-- 8< --
tree $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
lmtx/
└── luatex-cache
└── context
└── 5fe67e0bfe781ce0dde776fb1556f32e
├── formats
│   └── luametatex
│   ├── cont-en.fmt
│   ├── cont-en.log
│   ├── cont-en.lui

Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Hans Hagen

On 9/11/2019 1:19 AM, Henri Menke wrote:

On 9/11/19 3:50 AM, Aditya Mahajan wrote:

On Tue, 10 Sep 2019, Hans Hagen wrote:


On 9/10/2019 4:11 PM, Vladimir Lomov wrote:

Hello,
today I updated lmtx and on simple

$ context --version

I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.

The context from Context Suite (mkiv) works fine.

P.S. I tested on two systems, both runs Archlinux x86_64.

can you completely wipe the texmf-cache directory and then run

mtxrun --generate
context --make

(there is a change in bytecode that gets not automatically noticed that
can give that crash)


I had the same issue and completely wiping the texmf-cache fixes it.

@Vladimir: If you are using the luametatex package from AUR, then the
texmf-cache is located at $HOME/.cache/luametatex.


I'm receiving the super helpful error message:

 ! error (lua): function call: no


there is not much context to present there as it means that deep down a 
bad function token is expanded, something under control of the macro 
package, which then has/is messed up



Maybe some sort of cache versioning is in order to at least give a better error.


for now, adding

\ifdefined\pdfsavepos\else
\let\pdfsavepos \savepos
\let\pdflastxpos\lastxpos
\let\pdflastypos\lastypos
\fi

to cont-new.mkiv seems to work ok

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-11 Thread Hans Hagen



but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I
set it to $HOME/.cache/context-suite).





I'm receiving the super helpful error message:

 ! error (lua): function call: no

Maybe some sort of cache versioning is in order to at least give a better error.


It didn't occured to me that the problem may be with the cache, it would
be helpfull if context/luametatex will give error message, something
like "cache version mismatch" and exit.

hm, i have the same cache for both (different files are used)

so what does the tikz that fails look like (mwe)

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Vladimir Lomov
Hello,
** Henri Menke [2019-09-11 11:19:57 +1200]:

> On 9/11/19 3:50 AM, Aditya Mahajan wrote:
>> On Tue, 10 Sep 2019, Hans Hagen wrote:
>> 
>>> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
 Hello,
 today I updated lmtx and on simple

$ context --version

 I get segfault (in the same time luametatex --version works fine).
 Running under gdb shows me that the problem might be in one of 'realloc'
 calls.

 The context from Context Suite (mkiv) works fine.

 P.S. I tested on two systems, both runs Archlinux x86_64.
>>> can you completely wipe the texmf-cache directory and then run
>>>
>>> mtxrun --generate
>>> context --make
>>>
>>> (there is a change in bytecode that gets not automatically noticed that 
>>> can give that crash)
>> 
>> I had the same issue and completely wiping the texmf-cache fixes it.
>> 
>> @Vladimir: If you are using the luametatex package from AUR, then the 
>> texmf-cache is located at $HOME/.cache/luametatex.

No, I don't use the package from AUR, I simply do

  /usr/local/opt/lmtx $ sudo ./install.sh

but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I
set it to $HOME/.cache/context-suite).

> I'm receiving the super helpful error message:
> 
> ! error (lua): function call: no
> 
> Maybe some sort of cache versioning is in order to at least give a better 
> error.

It didn't occured to me that the problem may be with the cache, it would
be helpfull if context/luametatex will give error message, something
like "cache version mismatch" and exit.

> Cheers, Henri
> 
>> 
>> Aditya

---
WBR, Vladimir Lomov



-- 
Sometimes I live in the country,
And sometimes I live in town.
And sometimes I have a great notion,
To jump in the river and drown.


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Vladimir Lomov
Hello,
** Hans Hagen [2019-09-10 17:18:45 +0200]:

> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
>> Hello,
>> today I updated lmtx and on simple
>>$ context --version
>> 
>> I get segfault (in the same time luametatex --version works fine).
>> Running under gdb shows me that the problem might be in one of 'realloc'
>> calls.
>> 
>> The context from Context Suite (mkiv) works fine.
>> 
>> P.S. I tested on two systems, both runs Archlinux x86_64.
> can you completely wipe the texmf-cache directory and then run
> 
> mtxrun --generate
> context --make
> 
> (there is a change in bytecode that gets not automatically noticed that can
> give that crash)

Yes, that "fixed" the problem, thank you.

> Hans
> 
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -

---
WBR, Vladimir Lomov

-- 
Got a wife and kids in Baltimore Jack,
I went out for a ride and never came back.
Like a river that don't know where it's flowing,
I took a wrong turn and I just kept going.

Everybody's got a hungry heart.
Everybody's got a hungry heart.
Lay down your money and you play your part,
Everybody's got a hungry heart.

I met her in a Kingstown bar,
We fell in love, I knew it had to end.
We took what we had and we ripped it apart,
Now here I am down in Kingstown again.

Everybody needs a place to rest,
Everybody wants to have a home.
Don't make no difference what nobody says,
Ain't nobody likes to be alone.
-- Bruce Springsteen, "Hungry Heart"


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Henri Menke
On 9/11/19 3:50 AM, Aditya Mahajan wrote:
> On Tue, 10 Sep 2019, Hans Hagen wrote:
> 
>> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
>>> Hello,
>>> today I updated lmtx and on simple
>>>
>>>$ context --version
>>>
>>> I get segfault (in the same time luametatex --version works fine).
>>> Running under gdb shows me that the problem might be in one of 'realloc'
>>> calls.
>>>
>>> The context from Context Suite (mkiv) works fine.
>>>
>>> P.S. I tested on two systems, both runs Archlinux x86_64.
>> can you completely wipe the texmf-cache directory and then run
>>
>> mtxrun --generate
>> context --make
>>
>> (there is a change in bytecode that gets not automatically noticed that 
>> can give that crash)
> 
> I had the same issue and completely wiping the texmf-cache fixes it.
> 
> @Vladimir: If you are using the luametatex package from AUR, then the 
> texmf-cache is located at $HOME/.cache/luametatex.

I'm receiving the super helpful error message:

! error (lua): function call: no

Maybe some sort of cache versioning is in order to at least give a better error.

Cheers, Henri

> 
> Aditya
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___
> 



signature.asc
Description: OpenPGP digital signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Aditya Mahajan

On Tue, 10 Sep 2019, Hans Hagen wrote:


On 9/10/2019 4:11 PM, Vladimir Lomov wrote:

Hello,
today I updated lmtx and on simple

   $ context --version

I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.

The context from Context Suite (mkiv) works fine.

P.S. I tested on two systems, both runs Archlinux x86_64.

can you completely wipe the texmf-cache directory and then run

mtxrun --generate
context --make

(there is a change in bytecode that gets not automatically noticed that 
can give that crash)


I had the same issue and completely wiping the texmf-cache fixes it.

@Vladimir: If you are using the luametatex package from AUR, then the 
texmf-cache is located at $HOME/.cache/luametatex.


Aditya
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Hans Hagen

On 9/10/2019 4:11 PM, Vladimir Lomov wrote:

Hello,
today I updated lmtx and on simple
   
   $ context --version


I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.

The context from Context Suite (mkiv) works fine.

P.S. I tested on two systems, both runs Archlinux x86_64.

can you completely wipe the texmf-cache directory and then run

mtxrun --generate
context --make

(there is a change in bytecode that gets not automatically noticed that 
can give that crash)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] context (lmtx) segfaults on x86_64 linux

2019-09-10 Thread Vladimir Lomov
Hello,
today I updated lmtx and on simple
  
  $ context --version

I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.

The context from Context Suite (mkiv) works fine.

P.S. I tested on two systems, both runs Archlinux x86_64.

---
WBR, Vladimir Lomov

-- 
Carelessly planned projects take three times longer to complete than expected.
Carefully planned projects take four times longer to complete than expected,
mostly because the planners expect their planning to reduce the time it takes.


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] context lmtx

2019-04-08 Thread Hans Hagen

Hi,

As some (and hopefully more) users are testing lmtx, here is some more 
information about what to watch for.


- There are no changes at the macro level that would not have occurred 
at some point when using luatex. For instance, if \pagewidth doesn't 
work, that is because it is now simply gone, while before it was a 
temporary compatibility hack. It is some backend related measure that 
did more good than bad and was never meant for users.


- In MkIV most of the backend code is done in Lua, and ConTeXt never 
used much of the engine. We now simply do all backend stuff in Lua. That 
also means that the pdf.* namespace is no longer supposed to be used at 
the user level. It might get hidden completely at some point, or maybe 
emulated to some extend but again, that was never meant to be a user 
level interface (in context).


- The same is true for images. I might decide to keep the img namespace 
but we have different mechanisms so again, img was never meant for user 
level usage (in context). In lmtx the engine is no longer really 
involved in image inclusion at all (so we went from 'some' to 'none' in 
context).


- Directions (there was some message about that) have a high level 
interface that should be used because there can be interferences 
otherwise (read: therefore no support for low level hacking). The 
directional model in luametatex has been overhauled and to what extent i 
will backport that to luatex is undecided (think of compatibility 
issues; it also depends on further experiments; and after all, it works 
ok in luatex) but that should not affect mkiv (and using luatex).


- Font handling was already under Lua control in context so nothing 
changed there apart from that also tfm loading is now delegated (but i 
suppose that not many users use tfm fonts). The new setup will provide 
some interesting new options that will be explored in the future but 
there we're talking of non-typical usage (for those wondering about 
generic usage of the font loader: we could always do some more in 
context so the generic usage is not affected.)


- Performance is in hit by all this because a lua backend is of course 
slower than native c but we gain a back in other areas, so overall 
performance is not touched (and actually a lot can be gained due to 
other side effects; the same is true for the memory footprint; now that 
luatex 1.10 is out I can also use some of its features.).


- Some problems reported (like clash in cache) are easy to solve. As are 
some more tricky things like the page injection mechanism, which just 
happens to depend on alternative low level backend code. I suppose more 
issues like those will show up in the coming weeks.


- Let me stress that deep down there is still the normal TeX engine, 
token handler, memory management, macro machinery at work and it will 
stay as such because nothing can beat the core tex performance. At the 
macro level context is rather optimized for using it and just in case 
one wonders if we could benefit from further luafication, the answer is 
'no' because as said, tex parsing (and expansion) is very fast, as is 
the grouping model (which is fundamental to tex). So, we have (and keep) 
the same hybrid lua, tex, mp model as we already have for over a decade. 
We use each language for what it is best.


- When all users have moved to luametatex i might clean up some code 
that now is kept around for compatibility (just because, the less code 
the better, and we can always make a frozen snapshot). But that is 
something that will go mostly unnoticed.


So, thanks for testing, and please keep testing,

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___