Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Joerg Sonnenberger
On Sun, Jan 20, 2019 at 11:29:29AM +0100, Marc Balmer wrote: > > > > Am 20.01.2019 um 11:14 schrieb Kamil Rytarowski : > > > > On 20.01.2019 11:03, Martin Husemann wrote: > >> On Sun, Jan 20, 2019 at 10:32:43AM +0100, Kamil Rytarowski wrote: > >>> I find it as workaround of our libc behavior. >

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Marc Balmer
> Am 20.01.2019 um 11:14 schrieb Kamil Rytarowski : > > On 20.01.2019 11:03, Martin Husemann wrote: >> On Sun, Jan 20, 2019 at 10:32:43AM +0100, Kamil Rytarowski wrote: >>> I find it as workaround of our libc behavior. >> >> I disagree, there is no clean way to implement the call-on-dlclose >>

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Kamil Rytarowski
On 20.01.2019 11:03, Martin Husemann wrote: > On Sun, Jan 20, 2019 at 10:32:43AM +0100, Kamil Rytarowski wrote: >> I find it as workaround of our libc behavior. > > I disagree, there is no clean way to implement the call-on-dlclose > semantics (i.e. it needs disgusting ld.elf_so hacks and layer vi

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Martin Husemann
On Sun, Jan 20, 2019 at 10:32:43AM +0100, Kamil Rytarowski wrote: > I find it as workaround of our libc behavior. I disagree, there is no clean way to implement the call-on-dlclose semantics (i.e. it needs disgusting ld.elf_so hacks and layer violations). But maybe we should document the __cxa_at

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Kamil Rytarowski
On 20.01.2019 10:19, Marc Balmer wrote: > > >> Am 20.01.2019 um 10:14 schrieb Martin Husemann : >> >> On Sun, Jan 20, 2019 at 10:06:33AM +0100, Marc Balmer wrote: >>> Why are atexit handlers run after dlclosing loaded libraries? That sounds >>> wrong to me, but is there a reason? >> >> They are

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Marc Balmer
> Am 20.01.2019 um 10:14 schrieb Martin Husemann : > > On Sun, Jan 20, 2019 at 10:06:33AM +0100, Marc Balmer wrote: >> Why are atexit handlers run after dlclosing loaded libraries? That sounds >> wrong to me, but is there a reason? > > They are run at exit(1) time, the application (or in thi

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Martin Husemann
On Sun, Jan 20, 2019 at 10:06:33AM +0100, Marc Balmer wrote: > Why are atexit handlers run after dlclosing loaded libraries? That sounds > wrong to me, but is there a reason? They are run at exit(1) time, the application (or in this case library) is responsible of removing them if it dlclose()s

Re: Lua shared object asymmetry loading Xlib.

2019-01-20 Thread Marc Balmer
> Am 04.01.2019 um 19:29 schrieb Valery Ushakov : > > On Wed, Dec 26, 2018 at 09:44:53 -0900, Phil Rulon wrote: > >> msd$ /usr/bin/lua -v test.lua >> Lua 5.3.3 Copyright (C) 1994-2016 Lua.org, PUC-Rio >> table >> function >> [1] Segmentation fault (core dumped) /usr/bin/lua -v test.lua >>