RE: Anyone using Decoda IDE? (Question for Paul K.)

Hi Peter

Yes I am a big fan of ZeroBrane Studio, its author is extremely helpful with any questions and bug reports.
I recall pointing out a couple of small bugs I noticed a few months back, Paul replied within a matter of hours and fixed it in a day or so !!

My problem is that I need to debug Lua source code that has tons of calls to my own custom C API functions, of course I cant debug that source in isolation as those functions don't exist. I need to be able to debug the source as it executes in its EXE environment. LuaStudio allows me to do that by attaching to the exe, this facility is not present in ZBS.

I could probably achieve the same goal using ZBS if my PC exe had an Ethernet capability and could run LuaSocket. It hasn't, so I am snookered on that solution.

I wonder if Paul Kulchenko has considered adding the ability to attach to a running process ? It would have to be a specific PC only feature though. It Would be a fantastic feature if its possible ?

Geoff

Date: Sat, 8 Jun 2013 15:43:46 -0400
From: xingdaoshuiqongchu@gmail.com
To: lua-l@lists.lua.org
Subject: Re: Anyone using Decoda IDE?

If you are not restricted to Decoda, you might try ZeroBranes instead. It is a green program on windows. Just download and extract the windows binary, no trick and hassle

http://studio.zerobrane.com/

On Sat, Jun 8, 2013 at 6:49 AM, Geoff Smith <spammealot1@live.co.uk> wrote:

Hi

I have a PC exe file (built using VS2008) that has Lua statically linked inside it, I am trying to debug a Lua script using Decoda, but so far no joy at all in managing to set and hit a breakpoint in the script. I have tried running it just using the normal run with debug and pointing Decoda at my "test.exe" and my "test.pdb" files. Also I have tried starting up the exe first and then attaching to the running process. I can attach OK to the process but I get this error message

Warning 1002: Symbol file 'C:\Windows\syswow64\msvcrt.pdb' located but it does not match module 'C:\Windows\syswow64\msvcrt.dll'

The breakpoint I set on a specific line seems to get cleared and reset to line 1 of the script file and never gets hit anyway.

I have now proved that it is possible to debug a Lua script running in Lua inside my exe as last week I downloaded LuaStudio (The Chinese commercial one not the open source one on Github). I must confess I wasn't expecting too much from it, due to the English/Chinese language difficulties. I was wrong ! It is rather a nice tool, and the ability to debug a statically linked Lua exe works great, really easy to set up and pretty robust. Its just a shame its not an open source tool.
Don't bother checking it out if you are using Lua 5.2, or like good detailed docs or an English Users forum. It lacks all of those items

So I know the problem in debugging my script is fundamentally solvable, just got to figure out what the problem is with the Decoda way of doing it

I have got all sorts of MS msvcrt.dll & msvcrt.pdb's in my system folder from different versions of Visual Studio. maybe I have got some sort of mismatch there that trips up Decoda.

Any thoughts on how to solve this issue would be appreciated. Thanks

Geoff