Crash in CallCDeclFunction*/asm volatile on MacOS 32-bit and not in 64-bit

Simon Geilfus · 2014-02-27T21:59:24

Hi, First of all thank you for this great library! I discovered it a few days ago, and I don't think I'll be able to look back! I'm having a few issues trying to make it work in 32-bit (i386) with XCode 5 and OSX 10.9. Everything works great in 64-bit and it doesn't seem to change anything to build the library in 32 or 64 bit, a crash always happen in the same file if I try to run the application in 32-bit. I've found a post on the forum from a few years ago that seams to be related to my problem as everything seems to happen in that same CallCDeclFunctionObjLast, but what I found in the post didn't helped and that bug seems to have been corrected since a few release anyway (that was in 2012!). If it's relevant, I think that the function the engine is trying to execute is the constructor of an object I registered that way: template<typename T, typename P1, typename P2> static void constructor(P1 p1, P2 p2, T* ptr) { new (ptr) T(p1,p2); } r = engine->RegisterObjectBehaviour(name.c_str(), asBEHAVE_CONSTRUCT, ( "void f("+type+","+type+")" ).c_str(), asFUNCTION((BindingHelper::constructor<ci::Vec2<T>,T,T>)), asCALL_CDECL_OBJLAST); assert( r >= 0 ); Actually if I build the library without any debug symbols the only message I got is "error: memory read failed for 0xd04fae00" so that might have something to do with how I handle constructors (which seem to be the way to do it according to the wiki) So basically I'm a bit lost and wanted to know if that's a known issue, if anyone experienced the same with XCode5/llvm/32bit or if I'm just doing something wrong in my script/binding code. Any suggestions are welcome! Thanks a lot! Simon.

AngelCode Affiliates

Started by simong February 16, 2014 11:34 AM

12 comments, last by simong 10 years, 1 month ago

WitchLord

4,834

February 16, 2014 11:42 PM

I think only a low-level debugging session would allow us to identify the cause. It would be necessary to examine at exactly which location the values become incorrect and the stack becomes misaligned.

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

simong

242

Author

February 17, 2014 10:32 AM

Hi Andreas,

I'm afraid asm/misaligned stack/... goes a bit beyond my understanding.

I uploaded a series of screenshots showing a few more steps and some values, but as I'm not sure what I'm looking for I don't know if it's any helpful.

On the other hand what I can do is ask for some feedback on libcinder forum and try to make some people test the xcode project. Just to make sure I'm not crazy and because it might be easier to find people with the same platform/frameworks/libraries over there.

Let me know if there's something I could do.

Thanks again!

WitchLord

4,834

February 17, 2014 01:29 PM

From the screenshots I can see that everything is correct up until the inline assembler code executes. The values passed into the CallCDeclFunction are as they should be, which would indicate that the problem really is somewhere within the inline assembler code.

If you can step through the inline assembler code instruction by instruction and show me the values of the affected registers, much like how you did with the C++ code before it I may be able to spot the problem.

Perhaps if you'd allow me to login to your machine remotely (for example, using something like logmein) I could do the debugging myself.

I very much doubt the problem is related to libcinder (unless they too have some assembler code that might mess with the CPU registers).

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

simong

242

Author

February 27, 2014 09:59 PM

Sorry for the late reply Andreas!

I finally ended up switching back to 64-bit.

I was talking about posting this to cinder forum to have people test it, just to make sure I didn't do something wrong. But as it seems to be really low level related it might be more on the compiler/xcode side...

If you still want to access my machine, I'll be happy to find a way to do that. I can give you my email address so we can figure out how to do it.

Thanks for the help anyway!

Crash in CallCDeclFunction*/asm volatile on MacOS 32-bit and not in 64-bit

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Crash in CallCDeclFunction*/asm __volatile__ on MacOS 32-bit and not in 64-bit

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines

Crash in CallCDeclFunction*/asm volatile on MacOS 32-bit and not in 64-bit