lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index] 

Hi Fred,

> but i wonder: shouldn't this error appear only when the current stack
> contains this kind of userdata value?

The Stack view includes all stack frames (so they need to be
serialized), so if any of them has this value as either upvalue or a
local value, you may get the error.

What version of mobdebug are you using? Is there a simple test case I
can run locally?

Paul

On Mon, Mar 11, 2013 at 1:50 PM, Frederico Rodrigues Abraham
<devotion97@gmail.com> wrote:
> i see.
> i am indeed using a new tolua version, which adds the '#' operator for
> some objects created by tolua.
> but i wonder: shouldn't this error appear only when the current stack
> contains this kind of userdata value?
>
> thank you,
> -- Fred
>
> On Mon, Mar 11, 2013 at 5:40 PM, Paul K <paulclinger@yahoo.com> wrote:
>> Hi Frederico,
>>
>>> "Error: src/lbase/mobdebug.lua:166: Attempt to perform operation on an
>>> invalid operand"
>>
>> This doesn't seem like something that Lua or mobdebug would report.
>> This looks like an error message from tolua, probably related to an
>> attempt from mobdebug to serialize userdata values you have in your
>> script.
>>
>> There are some improvements for mobdebug currently being tested that
>> add processing of __tostring and __serialize methods for userdata
>> values, but I'm not sure if they help with this particular issue as
>> I've never seen it before.
>>
>> Paul.
>>
>> On Mon, Mar 11, 2013 at 1:12 PM, Frederico Rodrigues Abraham
>> <devotion97@gmail.com> wrote:
>>> hi.
>>> is the stack window operational?
>>> i get the following stack window message:
>>>
>>> "Error: src/lbase/mobdebug.lua:166: Attempt to perform operation on an
>>> invalid operand"
>>>
>>> system: client: windows, lua 5.2, server: windows with remote debugging
>>>
>>> greets,
>>> -- Fred
>>>
>>>
>>>
>>> On Fri, Jan 18, 2013 at 10:16 PM, Paul K <paulclinger@yahoo.com> wrote:
>>>> Hi All,
>>>>
>>>> I have committed several changes to ZeroBrane Studio and MobDebug that
>>>> may be of interest:
>>>>
>>>> 1. MobDebug and ZBS now support Lua 5.2 debugging. ZBS is still
>>>> packaged with Lua 5.1.5, but you can debug Lua 5.2 applications from
>>>> it if you configure "path.lua" to point to your Lua 5.2 executable
>>>> (you will also need luasocket compiled for Lua 5.2)
>>>> 2. MobDebug and ZBS now support code reloading, coroutine debugging,
>>>> and live-coding under LuaJIT. For the reloading and live coding you'd
>>>> need to use some recent version of LuaJIT as this functionality
>>>> requires this commit
>>>> (http://repo.or.cz/w/luajit-2.0.git/commit/e422ae2d9d184592066c1252ba0b391c4a1830ba)
>>>> to be included. This means that if you configure "path.lua" to point
>>>> to your LuaJIT executable, you can use regular commands from the IDE
>>>> to debug your scripts.
>>>> 3. MobDebug has been updated to work with the most recent luasocket
>>>> that has Lua 5.2 support (unstable branch
>>>> https://github.com/diegonehab/luasocket/tree/unstable); tested on
>>>> Windows with Lua 5.2.
>>>> 4. MobDebug and ZBS now support cross-platform remote debugging; you
>>>> can have your app and the IDE running on two different filesystems.
>>>> This allows to debug a Lua app running on Raspberry-pi from ZBS
>>>> running on a Windows or an OSX computer. This doesn't require any
>>>> configuration as the IDE will attempt to map the remote path to the
>>>> project folder you are using in ZBS (you will see a message when the
>>>> mapping is successful); you just need to have your Lua project files
>>>> present in both locations.
>>>>
>>>> You can get both from GitHub: ZBS
>>>> https://github.com/pkulchenko/ZeroBraneStudio (this includes MobDebug
>>>> too) or MobDebug https://github.com/pkulchenko/MobDebug. Please email
>>>> me or open a ticket on github if you notice any issues. Thank you!
>>>>
>>>> Paul.
>>>> - ZeroBrane Studio - slick Lua IDE and debugger for Windows, OSX, and
>>>> Linux - http://studio.zerobrane.com/
>>>>
>>>
>>
>