Re: lua-l Digest, Vol 91, Issue 1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: lua-l Digest, Vol 91, Issue 1

daveaceinc
paige,

Thank you for your reply.

The engine was written in C++ and is a custom engine used in our company for many years. There are no debug facilities in the C++ code per say. And they don't let us mess with it. 

I think you got my problem exactly! lua debuggers don't work because without the source the lua scripts are meaningless. There is a disconnect between the source code in engine and the lua scripts.

If I were to somehow magically get a hold of the engine's c+ source code. Then what  do I use to debug? I want to be able to have break points and step in my lua scripts as its running in debug mode. 

Lua editors such as Zerobrane for instance don't run C++ code. And vice versa C++ editors such as Visual Studio don't run Lua. Or do they? If so what would be the setup?

I appreciate your thoughts.

Dave.

-----Original Message-----
From: lua-l-request <[hidden email]>
To: lua-l <[hidden email]>
Sent: Wed, Jan 31, 2018 6:26 pm
Subject: lua-l Digest, Vol 91, Issue 1

Send lua-l mailing list submissions to
lua-[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org

or, via email, send a message with subject or body 'help' to
lua-l-[hidden email]

You can reach the person managing the list at
lua-l-[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lua-l digest..."


Today's Topics:

1. Re: Debug Lua embeded without access to c++ source (Paige DePol)
2. Re: Building torch7 (Dibyendu Majumdar)
3. Re: Building torch7 (Paul K)
4. Re: Building torch7 (Dibyendu Majumdar)
5. Re: Building torch7 (Dibyendu Majumdar)
6. Re: Building torch7 (Paige DePol)
7. Re: lpeg re.lua bug and provided fix (albertmcchan)
8. Re: Building torch7 (Italo Maia)


----------------------------------------------------------------------

Message: 1
Date: Wed, 31 Jan 2018 15:00:11 -0600
From: Paige DePol <[hidden email]>
Subject: Re: Debug Lua embeded without access to c++ source
To: Lua mailing list <lua-[hidden email]>
Message-ID: <14F8B077-0070-4004-888B-[hidden email]>
Content-Type: text/plain; charset=us-ascii

[hidden email] wrote:

> Here is the problem. We haven;t been able to find a way to debug ( break
> points, step thru, etc). As the program is being run to see if our lua
> script is having any bugs and if so where the bug is. So what happens is
> that if there is an issue it crashes and we have to trace our steps back
> and try to find the bug. Very painful and time consuming.
>
> If we had access to the c++ engine, we could have just loaded it to say
> Visual studio, add our lua files and debug while its running. But we don't
>
> So I am on a mission to find a way for us to debug. Any ideas you might
> have are greatly appreciated.

I am not sure you will find a way to debug your Lua scripts directly with
the engine unless the engine itself provides some sort of debugging hooks.

Which engine are you using? Have you tried to contact them to inquire about
debugging capabilities for Lua scripts? There are a number of programs out
there for Lua to allow you to edit and run scripts, however, unless they
know how to interface with your game engine they won't be of much help.

Usually game engines that come as "black boxes", where you only have the
game engine to run itself without sources, have some sort of facility to
enter a debugging mode... or come with a special debugging version of
the engine you can run while developing. Another issue is that standalone
Lua editors will not have access to the libraries present in the game
engine, making debugging scripts externally pretty much impossible.

I would suggest trying to contact the vendor of the game engine as they
will be more in a position to help you with your debugging issues.

Good luck with your game!

~Paige





------------------------------

Message: 2
Date: Wed, 31 Jan 2018 21:09:18 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxcTYvKE_2O3xOgVEmoRM_fCSx=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 08:00, p. shkadzko <[hidden email]> wrote:
> Can you be more specific?
> I am using ���Torch on a daily basis.
>

Hi, it is good to know that torch works with Lua 5.3. I was able
successfully build torch7 (the core library only) for Ravi which is a
Lua 5.3 derivative. However when trying to run a test I face a couple
of issues. The first one is this strange call:

require "paths"
paths.require "libtorch"

The paths.lua script is generated from:
https://github.com/torch/torch7/blob/master/paths.lua.in

I must be missing something here.

Second issue I am still investigating. While initializing torch I get
an error that I was surprised to see - it is do with exceeding the
number of max upvalues; this is set to 120 in Ravi. I have to work out
whether this is what it appears or something else.

Regards
Dibyendu



------------------------------

Message: 3
Date: Wed, 31 Jan 2018 14:03:30 -0800
From: Paul K <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CADUw5q0nx4veBF=OShz1pj_hU5RZZY-[hidden email]>
Content-Type: text/plain; charset="UTF-8"

> require "paths"
> paths.require "libtorch"

> The paths.lua script is generated from:
> https://github.com/torch/torch7/blob/master/paths.lua.in
> I must be missing something here.

I think it's a different paths module. I'd expect it to be this one:
https://github.com/torch/paths

Paul.

On Wed, Jan 31, 2018 at 1:09 PM, Dibyendu Majumdar
<[hidden email]> wrote:
> On 31 January 2018 at 08:00, p. shkadzko <[hidden email]> wrote:
>> Can you be more specific?
>> I am using ���Torch on a daily basis.
>>
>
> Hi, it is good to know that torch works with Lua 5.3. I was able
> successfully build torch7 (the core library only) for Ravi which is a
> Lua 5.3 derivative. However when trying to run a test I face a couple
> of issues. The first one is this strange call:
>
> require "paths"
> paths.require "libtorch"
>
> The paths.lua script is generated from:
> https://github.com/torch/torch7/blob/master/paths.lua.in
>
> I must be missing something here.
>
> Second issue I am still investigating. While initializing torch I get
> an error that I was surprised to see - it is do with exceeding the
> number of max upvalues; this is set to 120 in Ravi. I have to work out
> whether this is what it appears or something else.
>
> Regards
> Dibyendu
>



------------------------------

Message: 4
Date: Wed, 31 Jan 2018 22:04:59 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxdPYZcc=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 21:09, Dibyendu Majumdar <[hidden email]> wrote:
> Second issue I am still investigating. While initializing torch I get
> an error that I was surprised to see - it is do with exceeding the
> number of max upvalues; this is set to 120 in Ravi. I have to work out
> whether this is what it appears or something else.
>

Okay I found the issue here - in debug builds of Ravi I have 'ltests'
turned ON. Unfortunately this messes with some Lua settings. When apps
are linked against Ravi they don't see the messed up settings .. and
bang! the LUA_REGISTRYINDEX is not where the app thinks it is.
I guess I have have to make 'ltests' an explicit feature and not part
of all debug builds.

If you don't know what 'ltests' is then it is part of Lua's internal
testing infrastructure. When it is enabled it does a bunch of internal
checks and also exposes a library that can be used in tests cases. It
also amends some Lua settings making them more aggressive - hence the
problem above.


Regards



------------------------------

Message: 5
Date: Wed, 31 Jan 2018 22:08:58 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxc7mXwLEMMvYHvEcJ=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 22:03, Paul K <[hidden email]> wrote:
>> require "paths"
>> paths.require "libtorch"
>
>> The paths.lua script is generated from:
>> https://github.com/torch/torch7/blob/master/paths.lua.in
>> I must be missing something here.
>
> I think it's a different paths module. I'd expect it to be this one:
> https://github.com/torch/paths
>

Ah okay thanks! Strange that there is 'paths.lua' in the Lua script folder.

Regards
Dibyendu



------------------------------

Message: 6
Date: Wed, 31 Jan 2018 16:45:51 -0600
From: Paige DePol <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID: <2FCE0EC5-0F71-4494-BB2A-[hidden email]>
Content-Type: text/plain; charset=us-ascii

Dibyendu Majumdar <[hidden email]> wrote:

> On 31 January 2018 at 21:09, Dibyendu Majumdar <[hidden email]> wrote:
>> Second issue I am still investigating. While initializing torch I get
>> an error that I was surprised to see - it is do with exceeding the
>> number of max upvalues; this is set to 120 in Ravi. I have to work out
>> whether this is what it appears or something else.
>
> Okay I found the issue here - in debug builds of Ravi I have 'ltests'
> turned ON. Unfortunately this messes with some Lua settings. When apps
> are linked against Ravi they don't see the messed up settings .. and
> bang! the LUA_REGISTRYINDEX is not where the app thinks it is.
> I guess I have have to make 'ltests' an explicit feature and not part
> of all debug builds.
>
> If you don't know what 'ltests' is then it is part of Lua's internal
> testing infrastructure. When it is enabled it does a bunch of internal
> checks and also exposes a library that can be used in tests cases. It
> also amends some Lua settings making them more aggressive - hence the
> problem above.

LUA_REGISTRYINDEX is set relative to LUAI_MAXSTACK, normally the max
stack define is set to 15k for 32-bit or 1kk otherwise. Under 'ltests'
it is defined as 50k. Perhaps just changing this value to the default
value would allow you to keep 'ltests' enabled when linking?

~Paige






------------------------------

Message: 7
Date: Wed, 31 Jan 2018 18:29:14 -0500
From: albertmcchan <[hidden email]>
Subject: Re: lpeg re.lua bug and provided fix
To: Lua mailing list <lua-[hidden email]>
Message-ID: <4F7467FD-27FC-4400-A18A-[hidden email]>
Content-Type: text/plain; charset="us-ascii"

On Jan 31, 2018, at 8:40 AM, Roberto Ierusalimschy <[hidden email]-rio.br> wrote:

>>>> = re.match("aaand", "[a]^2")
>>>> .\re.lua: attempt to perform arithmetic on local 'p' (a string value)
>>>>
>>>> the fix is simple, just make sure class range ALWAYS return lpeg object
>>>
>>> Thanks for the report.
>>>
>>> -- Roberto
>>
>> BTW, a cleaner fix seems to be this:
>>
>> -local item = defined + Range + m.C(any)
>> +local item = defined + Range + m.P(any)
>>
>> Then, 'item' always results in a pattern.
>
> Sorry...
>
> -local item = defined + Range + m.C(any)
> +local item = defined + Range + m.C(any) / m.P
>
> -- Roberto
>

I think my original patch in the complement functon is safer, and more efficient

We do not need every item to be lpeg object, only its built class
(item were used ONLY to build class range)

one of item choice is defined, which included user defined constants
that may not be lpeg object. So, the bug is still there.

pat = re.compile("[%star]^10", {star = "*"})
.\re.lua: attempt to perform arithmetic on local 'p' (a string value)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listmaster.pepperfish.net/cgi-bin/mailman/private/lua-l-lists.lua.org/attachments/20180131/a823a3b8/attachment-0001.html

------------------------------

Message: 8
Date: Wed, 31 Jan 2018 21:25:48 -0300
From: Italo Maia <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<[hidden email]>
Content-Type: text/plain; charset="utf-8"

SGVsbG8gc2hrYWR6a28sIHRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrLiBBIGZldyBvZiB0aG9zZSBy
b2NrcyBkbyBpbnN0YWxsLgpIYWQgc29tZSBDVURBIGRlcGVuZGVuY3kgaXNzdWVzLCB0aG91Z2gu
CgoyMDE4LTAxLTMxIDk6NTcgR01ULTAzOjAwIHAuIHNoa2FkemtvIDxwLnNoa2FkemtvQGdtYWls
LmNvbT46Cgo+IEhlcmUgaXMgYSBsaXN0IG9mIGFkZGl0aW9uYWwgTHVhIGFuZCBUb3JjaCBkZXBl
bmRlbmNpZXMgdGhhdCBJIHVzZS4KPiBZb3UgY2FuIHBpY2sgd2hhdGV2ZXIgeW91IGZlZWwgeW91
IG1pZ2h0IG5lZWQuCj4KPiAjIGluc3RhbGwgdG9yY2gKPiBSVU4gZ2l0IGNsb25lIGh0dHBzOi8v
Z2l0aHViLmNvbS90b3JjaC9kaXN0cm8uZ2l0IC90b3JjaCAtLXJlY3Vyc2l2ZSBcCj4gICAgICYm
IGNkIC90b3JjaCBcCj4gICAgICYmIC4vaW5zdGFsbC5zaCBcCj4gICAgICYmIGNkIC4uCj4KPiAj
IGluc3RhbGwgdG9yY2ggZGVwcwo+IFJVTiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5z
dGFsbCBkcG5uIFwKPiAgICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwg
b3B0aW0gXAo+ICAgICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBjdW5u
IFwKPiAgICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgY3Vkbm4gXAo+
ICAgICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBsdWF1dGY4IFwKPiAg
ICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgcGVubGlnaHQgXAo+ICAg
ICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBtb3NlcyBcCj4gICAgICYm
IC90b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIHRvcmNoeCBcCj4gICAgICYmIC90
b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGx1YS1janNvbiBcCj4gICAgICYmIC90
b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGNzdiBcCj4gICAgICYmIC90b3JjaC9p
bnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGF1dG9ncmFkIFwKPiAgICAgJiYgL3RvcmNoL2lu
c3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgZGF0YWxvYWQgXAo+ICAgICAmJiAvdG9yY2gvaW5z
dGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCB0b3JjaG5ldCBcCj4gICAgICYmIC90b3JjaC9pbnN0
YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGN1dG9yY2ggXAo+ICAgICAmJiAvdG9yY2gvaW5zdGFs
bC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBodHRwczovL3Jhdy5naXRodWJ1c2VyY29udGVudC4KPiBj
b20vS2FpeGhpbi90b3JjaC1wYXN0YWxvZy9tYXN0ZXIvcm9ja3MvcGFzdGFsb2ctc2NtLTEucm9j
a3NwZWMgXAo+ICAgICAmJiBnaXQgY2xvbmUgaHR0cHM6Ly9naXRodWIuY29tL0VsZW1lbnQtUmVz
ZWFyY2gvcm5uLmdpdCBcCj4gICAgICYmIGNkIHJubiBcCj4gICAgICYmIC90b3JjaC9pbnN0YWxs
L2Jpbi9sdWFyb2NrcyBtYWtlIHJvY2tzL3Jubi1zY20tMS5yb2Nrc3BlYyBcCj4gICAgICYmIGNk
IC4uIFwKPgo+IFRoZSBsYXRlc3QgVG9yY2ggZG9lcyBub3Qgc3VwcG9ydCBvbGQgcm5uIGNvZGUg
dGhhdCB1c2VzIEVsZW1lbnQtUmVzZWFyY2gKPiBjbGFzc2VzLgo+IEluIG9yZGVyIHRvIG1ha2Ug
eW91IG9sZGVyIHJlY3VycmVudCBtb2RlbHMgd29yayB5b3UgaGF2ZSB0byBpbnN0YWxsCj4gRWxl
bWVudC1SZXNlYXJjaC9ybm4gcGFja2FnZSBzZXBhcmF0ZWx5IG90aGVyd2lzZSBqdXN0IHVzZSAi
Cj4gL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIHJubiIuCj4KPiBCZXN0LAo+IFBhdmVsCj4K
Pgo+IE9uIFdlZCwgSmFuIDMxLCAyMDE4IGF0IDEyOjMzIFBNLCBJdGFsbyBNYWlhIDxpdGFsby5t
YWlhQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gSG93IGRvIEkgaW5zdGFsbCB0aG9zZT8KPj4KPj4g
MjAxOC0wMS0zMSA4OjMxIEdNVC0wMzowMCBwLiBzaGthZHprbyA8cC5zaGthZHprb0BnbWFpbC5j
b20+Ogo+Pgo+Pj4gSGksIHlvdXIgZG9ja2VyaW1hZ2Ugd29uJ3Qgd29yayB3aXRoIG1vZGVscyB0
aGF0IHJlcXVpcmUgbm54IGFuZCBkcG5uIG9yCj4+PiB0aGUgcGFja2FnZXMgdGhhdCBhcmUgbm90
IGluc3RhbGxlZCBieSBzdGFuZGFyZCBpbnN0YWxsLnNoIHNjcmlwdC4gSXQgaXMKPj4+IGFsc28g
aW5jb21wYXRpYmxlIHdpdGggdGhlIG9sZGVyIGNvZGUgdGhhdCB1c2VzIHJubi7igI4KPj4+Cj4+
PiBTZW50IGZyb20gbXkgQmxhY2tCZXJyeSAxMCBzbWFydHBob25lLgo+Pj4gKkZyb206ICpJdGFs
byBNYWlhCj4+PiAqU2VudDogKldlZG5lc2RheSwgSmFudWFyeSAzMSwgMjAxOCAwMjo1Mgo+Pj4g
KlRvOiAqTHVhIG1haWxpbmcgbGlzdAo+Pj4gKlJlcGx5IFRvOiAqTHVhIG1haWxpbmcgbGlzdAo+
Pj4gKlN1YmplY3Q6ICpSZTogQnVpbGRpbmcgdG9yY2g3Cj4+Pgo+Pj4gSSBoYXZlOyBodHRwczov
L2dpdGh1Yi5jb20vaXRhbG9tYWlhL3RvcmNoLWRvY2tlcgo+Pj4KPj4+IDIwMTgtMDEtMzAgMTk6
NTQgR01ULTAzOjAwIERpYnllbmR1IE1hanVtZGFyIDxtb2JpbGVAbWFqdW1kYXIub3JnLnVrPjoK
Pj4+Cj4+Pj4gSGksCj4+Pj4KPj4+PiBIYXMgYW55b25lIHN1Y2Nlc3NmdWxseSBidWlsdCBUb3Jj
aDcgKGh0dHBzOi8vZ2l0aHViLmNvbS90b3JjaC90b3JjaDcpCj4+Pj4gd2l0aCBMdWEgNS4zPwo+
Pj4+Cj4+Pj4gVGhhbmtzIGFuZCBSZWdhcmRzCj4+Pj4gRGlieWVuZHUKPj4+Pgo+Pj4+Cj4+Pgo+
Pj4KPj4+IC0tCj4+PiAiQSBhcnJvZ8OibmNpYSDDqSBhIGFybWEgZG9zIGZyYWNvcy4iCj4+Pgo+
Pj4gPT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4+PiBNZS4gSXRhbG8gTW9yZWlyYSBDYW1w
ZWxvIE1haWEKPj4+IENvLWZ1bmRhZG9yIGRvIEdydXBvIGRlIFVzdcOhcmlvcyBQeXRob24gZG8g
Q2VhcsOhCj4+PiBTZWNyZXTDoXJpbyBGb3JIYWNrZXIgKGZiLmNvbS9Gb3JIYWNrZXJTcGFjZSkK
Pj4+IERlc2Vudm9sdmVkb3IgRnVsbC1TdGFjaywgRXNjcml0b3IsIEVtcHJlc8OhcmlvLCBWaXNp
b27DoXJpbwo+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0KPj4+IE1ldSBMaXZybyA8aHR0cDovL2JpdC5seS9mbGFzay1hbWF6b24+LCBTaXRl
IDxodHRwOi8vd3d3Lml0YWxvbWFpYS5jb20vPiwKPj4+IEJsb2cgPGh0dHA6Ly9ldXNvdW9sb2Jv
bWF1LmJsb2dzcG90LmNvbS8+Cj4+PiA9PT09PT09PT09PT09PT09PT09PT09PT09PT0KPj4+Cj4+
Pgo+Pgo+Pgo+PiAtLQo+PiAiQSBhcnJvZ8OibmNpYSDDqSBhIGFybWEgZG9zIGZyYWNvcy4iCj4+
Cj4+ID09PT09PT09PT09PT09PT09PT09PT09PT09PQo+PiBNZS4gSXRhbG8gTW9yZWlyYSBDYW1w
ZWxvIE1haWEKPj4gQ28tZnVuZGFkb3IgZG8gR3J1cG8gZGUgVXN1w6FyaW9zIFB5dGhvbiBkbyBD
ZWFyw6EKPj4gU2VjcmV0w6FyaW8gRm9ySGFja2VyIChmYi5jb20vRm9ySGFja2VyU3BhY2UpCj4+
IERlc2Vudm9sdmVkb3IgRnVsbC1TdGFjaywgRXNjcml0b3IsIEVtcHJlc8OhcmlvLCBWaXNpb27D
oXJpbwo+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQo+PiBNZXUgTGl2cm8gPGh0dHA6Ly9iaXQubHkvZmxhc2stYW1hem9uPiwgU2l0ZSA8aHR0
cDovL3d3dy5pdGFsb21haWEuY29tLz4sCj4+IEJsb2cgPGh0dHA6Ly9ldXNvdW9sb2JvbWF1LmJs
b2dzcG90LmNvbS8+Cj4+ID09PT09PT09PT09PT09PT09PT09PT09PT09PQo+Pgo+Cj4KCgotLSAK
IkEgYXJyb2fDom5jaWEgw6kgYSBhcm1hIGRvcyBmcmFjb3MuIgoKPT09PT09PT09PT09PT09PT09
PT09PT09PT09Ck1lLiBJdGFsbyBNb3JlaXJhIENhbXBlbG8gTWFpYQpDby1mdW5kYWRvciBkbyBH
cnVwbyBkZSBVc3XDoXJpb3MgUHl0aG9uIGRvIENlYXLDoQpTZWNyZXTDoXJpbyBGb3JIYWNrZXIg
KGZiLmNvbS9Gb3JIYWNrZXJTcGFjZSkKRGVzZW52b2x2ZWRvciBGdWxsLVN0YWNrLCBFc2NyaXRv
ciwgRW1wcmVzw6FyaW8sIFZpc2lvbsOhcmlvCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCk1ldSBMaXZybyA8aHR0cDovL2JpdC5seS9mbGFzay1h
bWF6b24+LCBTaXRlIDxodHRwOi8vd3d3Lml0YWxvbWFpYS5jb20vPiwKQmxvZyA8aHR0cDovL2V1
c291b2xvYm9tYXUuYmxvZ3Nwb3QuY29tLz4KPT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0t
LS0tLS0tLS0tLS0tIG5leHQgcGFydCAtLS0tLS0tLS0tLS0tLQpBbiBIVE1MIGF0dGFjaG1lbnQg
d2FzIHNjcnViYmVkLi4uClVSTDogaHR0cDovL2xpc3RtYXN0ZXIucGVwcGVyZmlzaC5uZXQvY2dp
LWJpbi9tYWlsbWFuL3ByaXZhdGUvbHVhLWwtbGlzdHMubHVhLm9yZy9hdHRhY2htZW50cy8yMDE4
MDEzMS9kZGU1NjJlZS9hdHRhY2htZW50Lmh0bWwK

------------------------------

_______________________________________________
lua-l mailing list
lua-[hidden email]
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org


End of lua-l Digest, Vol 91, Issue 1
************************************
Reply | Threaded
Open this post in threaded view
|

Re: lua-l Digest, Vol 91, Issue 1

Paige DePol
[hidden email] wrote:

> The engine was written in C++ and is a custom engine used in our company
> for many years. There are no debug facilities in the C++ code per say. And
> they don't let us mess with it.
>
> I think you got my problem exactly! lua debuggers don't work because
> without the source the lua scripts are meaningless. There is a disconnect
> between the source code in engine and the lua scripts.
>
> If I were to somehow magically get a hold of the engine's c+ source code.
> Then what do I use to debug? I want to be able to have break points and
> step in my lua scripts as its running in debug mode.
>
> Lua editors such as Zerobrane for instance don't run C++ code. And vice
> versa C++ editors such as Visual Studio don't run Lua. Or do they? If so
> what would be the setup?

Dave, when replying to the list from the digest format please, please
do not leave the entire digest message quoted in the reply. Delete all
but the specific portions of messages you are replying to.

So, the game engine you are using has no facilities for debugging
in any way at all as part of the game engine? That seems... bad! :(

Can you use sockets or read/write arbitrary files? As others have
mentioned, if you can use sockets or even just read/write to files
you could have some basic debugging capabilities.

When you have issues with your Lua scripts they are crashing the
game engine itself, without any diagnostic messages being emitted?

If you had access to the C++ source you would also have access to
the Lua engine, this would allow you to add any sort of debugger
that you would like. Or at least trap Lua script errors and prevent
the game engine from crashing outright. I do believe there are some
plugins for Visual Studio for Lua debugging, however, as Windows is
not the operating system I use for development I am not the best
person to answer that particular question.

So the creator of the game engine is the company you work for?
I guess I don't understand why those developers are unable to help
with debugging then. If the game engine has been in use for years
how have previous developers dealt with debugging their Lua scripts?
It really seems odd to me that there would be no facility for any
sort of debugging... I mean bugs are a normal part of development.

I wish I had some magic solution to assist you with debugging your
Lua scripts for your game engine... but really, the developers of
the game engine are the ones that should have these answers.

Best of luck to you in getting debugging working!

~Paige




Reply | Threaded
Open this post in threaded view
|

Re: lua-l Digest, Vol 91, Issue 1

daveaceinc
In reply to this post by daveaceinc
Heinrich,

I appreciate your reply and suggestion. However I have no idea how to inject a debugger into the code and your listed instructions are Greek to me. I am using Zerobrane for editing and debugging my lua scripts. Could you kindly send me step by step instruction on how to do this. I will be great full.

BTW: The link you have does not work.

Dave~



-----Original Message-----
From: lua-l-request <[hidden email]>
To: lua-l <[hidden email]>
Sent: Wed, Jan 31, 2018 6:26 pm
Subject: lua-l Digest, Vol 91, Issue 1

Send lua-l mailing list submissions to
lua-[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org

or, via email, send a message with subject or body 'help' to
lua-l-[hidden email]

You can reach the person managing the list at
lua-l-[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lua-l digest..."


Today's Topics:

1. Re: Debug Lua embeded without access to c++ source (Paige DePol)
2. Re: Building torch7 (Dibyendu Majumdar)
3. Re: Building torch7 (Paul K)
4. Re: Building torch7 (Dibyendu Majumdar)
5. Re: Building torch7 (Dibyendu Majumdar)
6. Re: Building torch7 (Paige DePol)
7. Re: lpeg re.lua bug and provided fix (albertmcchan)
8. Re: Building torch7 (Italo Maia)


----------------------------------------------------------------------

Message: 1
Date: Wed, 31 Jan 2018 15:00:11 -0600
From: Paige DePol <[hidden email]>
Subject: Re: Debug Lua embeded without access to c++ source
To: Lua mailing list <lua-[hidden email]>
Message-ID: <14F8B077-0070-4004-888B-[hidden email]>
Content-Type: text/plain; charset=us-ascii

[hidden email] wrote:

> Here is the problem. We haven;t been able to find a way to debug ( break
> points, step thru, etc). As the program is being run to see if our lua
> script is having any bugs and if so where the bug is. So what happens is
> that if there is an issue it crashes and we have to trace our steps back
> and try to find the bug. Very painful and time consuming.
>
> If we had access to the c++ engine, we could have just loaded it to say
> Visual studio, add our lua files and debug while its running. But we don't
>
> So I am on a mission to find a way for us to debug. Any ideas you might
> have are greatly appreciated.

I am not sure you will find a way to debug your Lua scripts directly with
the engine unless the engine itself provides some sort of debugging hooks.

Which engine are you using? Have you tried to contact them to inquire about
debugging capabilities for Lua scripts? There are a number of programs out
there for Lua to allow you to edit and run scripts, however, unless they
know how to interface with your game engine they won't be of much help.

Usually game engines that come as "black boxes", where you only have the
game engine to run itself without sources, have some sort of facility to
enter a debugging mode... or come with a special debugging version of
the engine you can run while developing. Another issue is that standalone
Lua editors will not have access to the libraries present in the game
engine, making debugging scripts externally pretty much impossible.

I would suggest trying to contact the vendor of the game engine as they
will be more in a position to help you with your debugging issues.

Good luck with your game!

~Paige





------------------------------

Message: 2
Date: Wed, 31 Jan 2018 21:09:18 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxcTYvKE_2O3xOgVEmoRM_fCSx=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 08:00, p. shkadzko <[hidden email]> wrote:
> Can you be more specific?
> I am using ���Torch on a daily basis.
>

Hi, it is good to know that torch works with Lua 5.3. I was able
successfully build torch7 (the core library only) for Ravi which is a
Lua 5.3 derivative. However when trying to run a test I face a couple
of issues. The first one is this strange call:

require "paths"
paths.require "libtorch"

The paths.lua script is generated from:
https://github.com/torch/torch7/blob/master/paths.lua.in

I must be missing something here.

Second issue I am still investigating. While initializing torch I get
an error that I was surprised to see - it is do with exceeding the
number of max upvalues; this is set to 120 in Ravi. I have to work out
whether this is what it appears or something else.

Regards
Dibyendu



------------------------------

Message: 3
Date: Wed, 31 Jan 2018 14:03:30 -0800
From: Paul K <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CADUw5q0nx4veBF=OShz1pj_hU5RZZY-[hidden email]>
Content-Type: text/plain; charset="UTF-8"

> require "paths"
> paths.require "libtorch"

> The paths.lua script is generated from:
> https://github.com/torch/torch7/blob/master/paths.lua.in
> I must be missing something here.

I think it's a different paths module. I'd expect it to be this one:
https://github.com/torch/paths

Paul.

On Wed, Jan 31, 2018 at 1:09 PM, Dibyendu Majumdar
<[hidden email]> wrote:
> On 31 January 2018 at 08:00, p. shkadzko <[hidden email]> wrote:
>> Can you be more specific?
>> I am using ���Torch on a daily basis.
>>
>
> Hi, it is good to know that torch works with Lua 5.3. I was able
> successfully build torch7 (the core library only) for Ravi which is a
> Lua 5.3 derivative. However when trying to run a test I face a couple
> of issues. The first one is this strange call:
>
> require "paths"
> paths.require "libtorch"
>
> The paths.lua script is generated from:
> https://github.com/torch/torch7/blob/master/paths.lua.in
>
> I must be missing something here.
>
> Second issue I am still investigating. While initializing torch I get
> an error that I was surprised to see - it is do with exceeding the
> number of max upvalues; this is set to 120 in Ravi. I have to work out
> whether this is what it appears or something else.
>
> Regards
> Dibyendu
>



------------------------------

Message: 4
Date: Wed, 31 Jan 2018 22:04:59 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxdPYZcc=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 21:09, Dibyendu Majumdar <[hidden email]> wrote:
> Second issue I am still investigating. While initializing torch I get
> an error that I was surprised to see - it is do with exceeding the
> number of max upvalues; this is set to 120 in Ravi. I have to work out
> whether this is what it appears or something else.
>

Okay I found the issue here - in debug builds of Ravi I have 'ltests'
turned ON. Unfortunately this messes with some Lua settings. When apps
are linked against Ravi they don't see the messed up settings .. and
bang! the LUA_REGISTRYINDEX is not where the app thinks it is.
I guess I have have to make 'ltests' an explicit feature and not part
of all debug builds.

If you don't know what 'ltests' is then it is part of Lua's internal
testing infrastructure. When it is enabled it does a bunch of internal
checks and also exposes a library that can be used in tests cases. It
also amends some Lua settings making them more aggressive - hence the
problem above.


Regards



------------------------------

Message: 5
Date: Wed, 31 Jan 2018 22:08:58 +0000
From: Dibyendu Majumdar <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<CACXZuxc7mXwLEMMvYHvEcJ=[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On 31 January 2018 at 22:03, Paul K <[hidden email]> wrote:
>> require "paths"
>> paths.require "libtorch"
>
>> The paths.lua script is generated from:
>> https://github.com/torch/torch7/blob/master/paths.lua.in
>> I must be missing something here.
>
> I think it's a different paths module. I'd expect it to be this one:
> https://github.com/torch/paths
>

Ah okay thanks! Strange that there is 'paths.lua' in the Lua script folder.

Regards
Dibyendu



------------------------------

Message: 6
Date: Wed, 31 Jan 2018 16:45:51 -0600
From: Paige DePol <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID: <2FCE0EC5-0F71-4494-BB2A-[hidden email]>
Content-Type: text/plain; charset=us-ascii

Dibyendu Majumdar <[hidden email]> wrote:

> On 31 January 2018 at 21:09, Dibyendu Majumdar <[hidden email]> wrote:
>> Second issue I am still investigating. While initializing torch I get
>> an error that I was surprised to see - it is do with exceeding the
>> number of max upvalues; this is set to 120 in Ravi. I have to work out
>> whether this is what it appears or something else.
>
> Okay I found the issue here - in debug builds of Ravi I have 'ltests'
> turned ON. Unfortunately this messes with some Lua settings. When apps
> are linked against Ravi they don't see the messed up settings .. and
> bang! the LUA_REGISTRYINDEX is not where the app thinks it is.
> I guess I have have to make 'ltests' an explicit feature and not part
> of all debug builds.
>
> If you don't know what 'ltests' is then it is part of Lua's internal
> testing infrastructure. When it is enabled it does a bunch of internal
> checks and also exposes a library that can be used in tests cases. It
> also amends some Lua settings making them more aggressive - hence the
> problem above.

LUA_REGISTRYINDEX is set relative to LUAI_MAXSTACK, normally the max
stack define is set to 15k for 32-bit or 1kk otherwise. Under 'ltests'
it is defined as 50k. Perhaps just changing this value to the default
value would allow you to keep 'ltests' enabled when linking?

~Paige






------------------------------

Message: 7
Date: Wed, 31 Jan 2018 18:29:14 -0500
From: albertmcchan <[hidden email]>
Subject: Re: lpeg re.lua bug and provided fix
To: Lua mailing list <lua-[hidden email]>
Message-ID: <4F7467FD-27FC-4400-A18A-[hidden email]>
Content-Type: text/plain; charset="us-ascii"

On Jan 31, 2018, at 8:40 AM, Roberto Ierusalimschy <[hidden email]-rio.br> wrote:

>>>> = re.match("aaand", "[a]^2")
>>>> .\re.lua: attempt to perform arithmetic on local 'p' (a string value)
>>>>
>>>> the fix is simple, just make sure class range ALWAYS return lpeg object
>>>
>>> Thanks for the report.
>>>
>>> -- Roberto
>>
>> BTW, a cleaner fix seems to be this:
>>
>> -local item = defined + Range + m.C(any)
>> +local item = defined + Range + m.P(any)
>>
>> Then, 'item' always results in a pattern.
>
> Sorry...
>
> -local item = defined + Range + m.C(any)
> +local item = defined + Range + m.C(any) / m.P
>
> -- Roberto
>

I think my original patch in the complement functon is safer, and more efficient

We do not need every item to be lpeg object, only its built class
(item were used ONLY to build class range)

one of item choice is defined, which included user defined constants
that may not be lpeg object. So, the bug is still there.

pat = re.compile("[%star]^10", {star = "*"})
.\re.lua: attempt to perform arithmetic on local 'p' (a string value)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listmaster.pepperfish.net/cgi-bin/mailman/private/lua-l-lists.lua.org/attachments/20180131/a823a3b8/attachment-0001.html

------------------------------

Message: 8
Date: Wed, 31 Jan 2018 21:25:48 -0300
From: Italo Maia <[hidden email]>
Subject: Re: Building torch7
To: Lua mailing list <lua-[hidden email]>
Message-ID:
<[hidden email]>
Content-Type: text/plain; charset="utf-8"

SGVsbG8gc2hrYWR6a28sIHRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrLiBBIGZldyBvZiB0aG9zZSBy
b2NrcyBkbyBpbnN0YWxsLgpIYWQgc29tZSBDVURBIGRlcGVuZGVuY3kgaXNzdWVzLCB0aG91Z2gu
CgoyMDE4LTAxLTMxIDk6NTcgR01ULTAzOjAwIHAuIHNoa2FkemtvIDxwLnNoa2FkemtvQGdtYWls
LmNvbT46Cgo+IEhlcmUgaXMgYSBsaXN0IG9mIGFkZGl0aW9uYWwgTHVhIGFuZCBUb3JjaCBkZXBl
bmRlbmNpZXMgdGhhdCBJIHVzZS4KPiBZb3UgY2FuIHBpY2sgd2hhdGV2ZXIgeW91IGZlZWwgeW91
IG1pZ2h0IG5lZWQuCj4KPiAjIGluc3RhbGwgdG9yY2gKPiBSVU4gZ2l0IGNsb25lIGh0dHBzOi8v
Z2l0aHViLmNvbS90b3JjaC9kaXN0cm8uZ2l0IC90b3JjaCAtLXJlY3Vyc2l2ZSBcCj4gICAgICYm
IGNkIC90b3JjaCBcCj4gICAgICYmIC4vaW5zdGFsbC5zaCBcCj4gICAgICYmIGNkIC4uCj4KPiAj
IGluc3RhbGwgdG9yY2ggZGVwcwo+IFJVTiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5z
dGFsbCBkcG5uIFwKPiAgICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwg
b3B0aW0gXAo+ICAgICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBjdW5u
IFwKPiAgICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgY3Vkbm4gXAo+
ICAgICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBsdWF1dGY4IFwKPiAg
ICAgJiYgL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgcGVubGlnaHQgXAo+ICAg
ICAmJiAvdG9yY2gvaW5zdGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBtb3NlcyBcCj4gICAgICYm
IC90b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIHRvcmNoeCBcCj4gICAgICYmIC90
b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGx1YS1janNvbiBcCj4gICAgICYmIC90
b3JjaC9pbnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGNzdiBcCj4gICAgICYmIC90b3JjaC9p
bnN0YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGF1dG9ncmFkIFwKPiAgICAgJiYgL3RvcmNoL2lu
c3RhbGwvYmluL2x1YXJvY2tzIGluc3RhbGwgZGF0YWxvYWQgXAo+ICAgICAmJiAvdG9yY2gvaW5z
dGFsbC9iaW4vbHVhcm9ja3MgaW5zdGFsbCB0b3JjaG5ldCBcCj4gICAgICYmIC90b3JjaC9pbnN0
YWxsL2Jpbi9sdWFyb2NrcyBpbnN0YWxsIGN1dG9yY2ggXAo+ICAgICAmJiAvdG9yY2gvaW5zdGFs
bC9iaW4vbHVhcm9ja3MgaW5zdGFsbCBodHRwczovL3Jhdy5naXRodWJ1c2VyY29udGVudC4KPiBj
b20vS2FpeGhpbi90b3JjaC1wYXN0YWxvZy9tYXN0ZXIvcm9ja3MvcGFzdGFsb2ctc2NtLTEucm9j
a3NwZWMgXAo+ICAgICAmJiBnaXQgY2xvbmUgaHR0cHM6Ly9naXRodWIuY29tL0VsZW1lbnQtUmVz
ZWFyY2gvcm5uLmdpdCBcCj4gICAgICYmIGNkIHJubiBcCj4gICAgICYmIC90b3JjaC9pbnN0YWxs
L2Jpbi9sdWFyb2NrcyBtYWtlIHJvY2tzL3Jubi1zY20tMS5yb2Nrc3BlYyBcCj4gICAgICYmIGNk
IC4uIFwKPgo+IFRoZSBsYXRlc3QgVG9yY2ggZG9lcyBub3Qgc3VwcG9ydCBvbGQgcm5uIGNvZGUg
dGhhdCB1c2VzIEVsZW1lbnQtUmVzZWFyY2gKPiBjbGFzc2VzLgo+IEluIG9yZGVyIHRvIG1ha2Ug
eW91IG9sZGVyIHJlY3VycmVudCBtb2RlbHMgd29yayB5b3UgaGF2ZSB0byBpbnN0YWxsCj4gRWxl
bWVudC1SZXNlYXJjaC9ybm4gcGFja2FnZSBzZXBhcmF0ZWx5IG90aGVyd2lzZSBqdXN0IHVzZSAi
Cj4gL3RvcmNoL2luc3RhbGwvYmluL2x1YXJvY2tzIHJubiIuCj4KPiBCZXN0LAo+IFBhdmVsCj4K
Pgo+IE9uIFdlZCwgSmFuIDMxLCAyMDE4IGF0IDEyOjMzIFBNLCBJdGFsbyBNYWlhIDxpdGFsby5t
YWlhQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gSG93IGRvIEkgaW5zdGFsbCB0aG9zZT8KPj4KPj4g
MjAxOC0wMS0zMSA4OjMxIEdNVC0wMzowMCBwLiBzaGthZHprbyA8cC5zaGthZHprb0BnbWFpbC5j
b20+Ogo+Pgo+Pj4gSGksIHlvdXIgZG9ja2VyaW1hZ2Ugd29uJ3Qgd29yayB3aXRoIG1vZGVscyB0
aGF0IHJlcXVpcmUgbm54IGFuZCBkcG5uIG9yCj4+PiB0aGUgcGFja2FnZXMgdGhhdCBhcmUgbm90
IGluc3RhbGxlZCBieSBzdGFuZGFyZCBpbnN0YWxsLnNoIHNjcmlwdC4gSXQgaXMKPj4+IGFsc28g
aW5jb21wYXRpYmxlIHdpdGggdGhlIG9sZGVyIGNvZGUgdGhhdCB1c2VzIHJubi7igI4KPj4+Cj4+
PiBTZW50IGZyb20gbXkgQmxhY2tCZXJyeSAxMCBzbWFydHBob25lLgo+Pj4gKkZyb206ICpJdGFs
byBNYWlhCj4+PiAqU2VudDogKldlZG5lc2RheSwgSmFudWFyeSAzMSwgMjAxOCAwMjo1Mgo+Pj4g
KlRvOiAqTHVhIG1haWxpbmcgbGlzdAo+Pj4gKlJlcGx5IFRvOiAqTHVhIG1haWxpbmcgbGlzdAo+
Pj4gKlN1YmplY3Q6ICpSZTogQnVpbGRpbmcgdG9yY2g3Cj4+Pgo+Pj4gSSBoYXZlOyBodHRwczov
L2dpdGh1Yi5jb20vaXRhbG9tYWlhL3RvcmNoLWRvY2tlcgo+Pj4KPj4+IDIwMTgtMDEtMzAgMTk6
NTQgR01ULTAzOjAwIERpYnllbmR1IE1hanVtZGFyIDxtb2JpbGVAbWFqdW1kYXIub3JnLnVrPjoK
Pj4+Cj4+Pj4gSGksCj4+Pj4KPj4+PiBIYXMgYW55b25lIHN1Y2Nlc3NmdWxseSBidWlsdCBUb3Jj
aDcgKGh0dHBzOi8vZ2l0aHViLmNvbS90b3JjaC90b3JjaDcpCj4+Pj4gd2l0aCBMdWEgNS4zPwo+
Pj4+Cj4+Pj4gVGhhbmtzIGFuZCBSZWdhcmRzCj4+Pj4gRGlieWVuZHUKPj4+Pgo+Pj4+Cj4+Pgo+
Pj4KPj4+IC0tCj4+PiAiQSBhcnJvZ8OibmNpYSDDqSBhIGFybWEgZG9zIGZyYWNvcy4iCj4+Pgo+
Pj4gPT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4+PiBNZS4gSXRhbG8gTW9yZWlyYSBDYW1w
ZWxvIE1haWEKPj4+IENvLWZ1bmRhZG9yIGRvIEdydXBvIGRlIFVzdcOhcmlvcyBQeXRob24gZG8g
Q2VhcsOhCj4+PiBTZWNyZXTDoXJpbyBGb3JIYWNrZXIgKGZiLmNvbS9Gb3JIYWNrZXJTcGFjZSkK
Pj4+IERlc2Vudm9sdmVkb3IgRnVsbC1TdGFjaywgRXNjcml0b3IsIEVtcHJlc8OhcmlvLCBWaXNp
b27DoXJpbwo+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0KPj4+IE1ldSBMaXZybyA8aHR0cDovL2JpdC5seS9mbGFzay1hbWF6b24+LCBTaXRl
IDxodHRwOi8vd3d3Lml0YWxvbWFpYS5jb20vPiwKPj4+IEJsb2cgPGh0dHA6Ly9ldXNvdW9sb2Jv
bWF1LmJsb2dzcG90LmNvbS8+Cj4+PiA9PT09PT09PT09PT09PT09PT09PT09PT09PT0KPj4+Cj4+
Pgo+Pgo+Pgo+PiAtLQo+PiAiQSBhcnJvZ8OibmNpYSDDqSBhIGFybWEgZG9zIGZyYWNvcy4iCj4+
Cj4+ID09PT09PT09PT09PT09PT09PT09PT09PT09PQo+PiBNZS4gSXRhbG8gTW9yZWlyYSBDYW1w
ZWxvIE1haWEKPj4gQ28tZnVuZGFkb3IgZG8gR3J1cG8gZGUgVXN1w6FyaW9zIFB5dGhvbiBkbyBD
ZWFyw6EKPj4gU2VjcmV0w6FyaW8gRm9ySGFja2VyIChmYi5jb20vRm9ySGFja2VyU3BhY2UpCj4+
IERlc2Vudm9sdmVkb3IgRnVsbC1TdGFjaywgRXNjcml0b3IsIEVtcHJlc8OhcmlvLCBWaXNpb27D
oXJpbwo+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQo+PiBNZXUgTGl2cm8gPGh0dHA6Ly9iaXQubHkvZmxhc2stYW1hem9uPiwgU2l0ZSA8aHR0
cDovL3d3dy5pdGFsb21haWEuY29tLz4sCj4+IEJsb2cgPGh0dHA6Ly9ldXNvdW9sb2JvbWF1LmJs
b2dzcG90LmNvbS8+Cj4+ID09PT09PT09PT09PT09PT09PT09PT09PT09PQo+Pgo+Cj4KCgotLSAK
IkEgYXJyb2fDom5jaWEgw6kgYSBhcm1hIGRvcyBmcmFjb3MuIgoKPT09PT09PT09PT09PT09PT09
PT09PT09PT09Ck1lLiBJdGFsbyBNb3JlaXJhIENhbXBlbG8gTWFpYQpDby1mdW5kYWRvciBkbyBH
cnVwbyBkZSBVc3XDoXJpb3MgUHl0aG9uIGRvIENlYXLDoQpTZWNyZXTDoXJpbyBGb3JIYWNrZXIg
KGZiLmNvbS9Gb3JIYWNrZXJTcGFjZSkKRGVzZW52b2x2ZWRvciBGdWxsLVN0YWNrLCBFc2NyaXRv
ciwgRW1wcmVzw6FyaW8sIFZpc2lvbsOhcmlvCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCk1ldSBMaXZybyA8aHR0cDovL2JpdC5seS9mbGFzay1h
bWF6b24+LCBTaXRlIDxodHRwOi8vd3d3Lml0YWxvbWFpYS5jb20vPiwKQmxvZyA8aHR0cDovL2V1
c291b2xvYm9tYXUuYmxvZ3Nwb3QuY29tLz4KPT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0t
LS0tLS0tLS0tLS0tIG5leHQgcGFydCAtLS0tLS0tLS0tLS0tLQpBbiBIVE1MIGF0dGFjaG1lbnQg
d2FzIHNjcnViYmVkLi4uClVSTDogaHR0cDovL2xpc3RtYXN0ZXIucGVwcGVyZmlzaC5uZXQvY2dp
LWJpbi9tYWlsbWFuL3ByaXZhdGUvbHVhLWwtbGlzdHMubHVhLm9yZy9hdHRhY2htZW50cy8yMDE4
MDEzMS9kZGU1NjJlZS9hdHRhY2htZW50Lmh0bWwK

------------------------------

_______________________________________________
lua-l mailing list
lua-[hidden email]
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org


End of lua-l Digest, Vol 91, Issue 1
************************************