unknownworlds / decoda Goto Github PK

Hi,
I found that when the application built by luajit is always crash when I get the information of some variable in Decoda. But when I replace luajit back to lua to build the application, it never happen.
It also happened when I set jit.off().
Could you help me on this?
Thanks a lot

Regards,
Cong Ling

Last beta crashes on any Windows without Visual Studio 2013.
(checked on Windows 7 and 8. After click on the link Decoda crashes).

Problem resolved after replacing msvcp120.dll and msvcr120.dll from redist VS2013 folder.

There are no option for changing the Lua files encoding. Decoda does not handle UTF-8 or UTF-16. It only supports the locale in non-Unicode characters only.

Decoda should handle the UTF-8 or UTF-16 properly.

I've been using Decoda for a while, and one issue has been that debugging will not work for 64-bit processes, requiring me to switch to the 32-bit build of my binary in order to debug Lua code. Now that Decoda is open source, it seems like this should possible to change. I would do it myself, but I'd like to find out what the stumbling blocks are to doing so.

The first road block appears to be that there are several static libraries in the repository, which I presume are built in 32-bit. Presumably, these need to be rebuilt in 64-bit as well - meaning that at the very least, 64-bit builds should be generated and imported. I know what most of them are, so I might be able to do that myself, but not all of them.

• Update - What is this? I have no idea.
• dbghelp - Microsoft's DbgHelp library. Static 64-bit libs are included with "Debugging Tools for Windows". I noticed though that the size of the 32-bit libs are not the same as the ones I have, so I'm not sure what version they're from.
• lua - Obviously Lua 5.1, should be easy - though I imagine it should be upgraded to Lua 5.2.1 at some point.
• tinyxml - The only one with a readme, stating it's available here. Again, though, I don't know what version it is.
• wxScintilla - Presumably this, but happily sources are included. I noticed that the included version of Scintilla is 1.62 which is very old (from 2004!)
• wxWidgets - Also includes source...with a million build targets, all set up for 32-bit. Hopefully it will work as 64-bit, though. Appears to be version 2.8.something?

Now, aside from all that, it's likely there are things in the debugger itself (LuaInject?) that need to change. I haven't delved into the code at all, so I don't know what awaits me.

Thoughts? Is anyone else interested in this who might want to collaborate?

anyone thinking about Linux or Mac installers for the future?

in DebugBackend.cpp line 3161:

sprintf(stack[i].name, "%s", symbol->Name);

should changed to:

_snprintf(stack[i].name, 256, "%s", symbol->Name);

Dear unknownworlds' devs

I'm drooling over decoda -- I'm using lua quite a bit, and the lack of real-life dev tools is a major pain.

Do you know how hard it would be to port Decoda to OS X, please?
Cheers.

When Lua 5.2 support?
I think many people want this.

Given the following snippet:

local string = require "string"

pcall(error, "some error")

print("hello world")
print("bar")

If I set a breakpoint on line 1, and then go step by step with F10 (Step Over), it works until I try to step over the line with pcall. At that point it just runs until the end.

However, if I step with F11 (Step Into), I can step on each line with no problem.

Tested this with Decoda 1.16 and 1.17 (build 1035 beta 1), it behaves the same in both.

premake4.lua:9: attempt to call global 'vpaths' (a nil value)

using http://software.opensuse.org/package/premake4

and

Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio

Hi there,

I'm a researcher studying software evolution. As part of my current research, I'm studying the implications of open-sourcing a proprietary software, for instance, if the project succeed in attracting newcomers. However, I observed that some projects, like decoda, deleted their software history.

5eb2b94

Knowing that software history is indispensable for developers (e.g., developers need to refer to history several times a day), I would like to ask decoda developers the following four brief questions:

1. Why did you decide to not keep the software history?
2. Do the core developers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
3. Do the newcomers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
4. How does the lack of history impacted on software evolution? Does it placed any burden in understanding and evolving the software?

Thanks in advance for your collaboration,

Gustavo Pinto, PhD
http://www.gustavopinto.org

When checking project files in to git, the git on windows expects all text files to have CRLF line ends; the .deproj files break this, causing weird git behavior for these files.

Decoda should either use CRLF on windows, or provide an option to set whether to use CRLF or LF.

So we have two files called Constructor.lua in two different directories. They are both different files but they're named the same. I opened one and it shows up fine in Decoda, I try to open the other and it doesn't open. It just goes to the currently opened file of the same name.

Hi,

It's been several months now that bugfixes and other improvements have been proposed, without anything done about them.

I can understand that you may not have the time to manage Decoda maintenance, but in that case maybe it would be a good idea to open commit rights to other people if another maintainer manifests him/her-self?

If the official branch if left unattended for too long, I fear it will simply die. It would be better if a single endorsed version could be the reference instead of having everyone fork his own.

When switching between tabs, either by using Ctrl+Tab, or by mouse, the editor window loses focus, making it necessary to click inside the editor with the mouse. This is especially bothersome when there's text selected in the window and I want to interact with it, because clicking to gain focus will cancel the selection. Also, middle-click doesn't make the editor gain focus, if it is lost in this way.

the debug version of Decoda can't be launched in my computer,my os is windows 7, IDE is vc++2005.
I used the permake4 ,version 4.4-beta5 and the following commands to make the project:

premake4 --os=windows --platform=x32,vs2005

then used the VC++2005 open the project, build the solution and start the debugging,
the release is ok for launching. but the debug is not.

the message as below:
Unable to start program
'e:\xxx\bin\debug\Decoda.exe'
this application has failed to start because the application configuration is incorrect .review the manifest file for possible errors,reinstalling the application may fix this problem, for more details ,please see the application event log'

Does anybody know what is wrong in it ?