64-bit build

[academician]

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?

[maxmcguire]

Update is the library used for auto-updating Decoda. It's something we created and I'm planning on putting it up on GitHub soon. The biggest challenge will be in the backend though, which uses some features like inline assembly and naked functions which aren't available when compiling for 64-bit.

[academician]

Hm. Well, it's certainly something I'm willing to tackle. Assuming I can, is it even necessary to switch Decoda's build to 64-bit or just the debugger backend?

Edit: Never mind, reading the code of course it will.

[qq260327056]

hey, we arelooking forward to the 64bit decoda very very warmly.

I try to modify the assembly code, but it seems very hard -_-!

[benoit-germain]

I'm also more than interested in a 64 bits build. I have a few 3rd party libs for which I'll need a Lua binding someday, and they are only available to me as 64 bits builds. Being able to debug my bindings with Decoda would be a great help.

[Yang-Radiant]

Hi! I know it's been awhile, but do you have any updates on this? How far were you able to get towards a 64 bit version?

[StubbornSlug]

Update is the library used for auto-updating Decoda. It's something we created and I'm planning on putting it up on GitHub soon. The biggest challenge will be in the backend though, which uses some features like inline assembly and naked functions which aren't available when compiling for 64-bit.

five years have passed，did you had put the Update up on GitHub? i`m trying compiling for 64-bit too,I can try to deal with inline assembly and naked functions,but have no idea about library Update

[fsfod]

The Update library is not really needed any more you can just cherry pick the commits from my branch that remove it.

[StubbornSlug]

The Update library is not really needed any more you can just cherry pick the commits from my branch that remove it.
I had already removed it,I am still trying compiling for 64-bit.