• Advertisement
Sign in to follow this  

test feature fails in amd64

This topic is 2403 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

On amd64 (Debian Sid) test_feature segfaults.

When I debug, I see that it fails on the very first test:
if( TestDefaultArg::Test() ) goto failed; else printf("-- TestDefaultArg passed\n");

Semi-callstack:
test_defaultarg.cpp:
line 64: r = ExecuteString(engine, "main()", mod);
scripthelper.cpp:
line 154: r = execCtx->Execute();
as_context.cpp:
line 983: ExecuteNext();
line 1956: l_sp += CallSystemFunction(i, this, 0);
as_callfunc.cpp:
line 424: retQW = CallSystemFunctionNative(context, descr, obj, args, sysFunc->hostReturnInMemory ? retPointer : 0, retQW2);
as_callfunc_x64_gcc.cpp:
line 210: int callConv = sysFunc->callConv;

Doesn't look good.

This is latest svn trunk.

Share this post


Link to post
Share on other sites
Advertisement
Looks like Angelscript 2.20.1 makes my app work on my machine. :)
I will see if the test succeeds as well.

Share this post


Link to post
Share on other sites
It's not as bad as it sounds:
test_feature passes for Angelscript 2.21.0 :)
Which probably means that it broke just recently.

Share this post


Link to post
Share on other sites
The latest svn revision should pass all tests, as it does on my buildbot: http://angelscript.jeremyh.net/builders/Full-Linux-64/builds/148

Have you tried a full rebuild?

Share this post


Link to post
Share on other sites
You can always check the status of angelscript on linux at http://angelscript.jeremyh.net as its compiled and tested on every commit.

Share this post


Link to post
Share on other sites
By the place where the segmentation fault occurs 'int callConv = sysFunc->callConv;', I would follow Jeremy's suggestion to recompile the whole library. It has the looks of a mismatch between source version and compiled version, that somehow got past the linker.

Let me know if it still fails after that, and I'll try to look into it further.







Share this post


Link to post
Share on other sites
I *think* that it's fixed now. ;)

Actually a bit disappointing, because now I have to really dig into the reasons why my code works perfectly on Windows, but fails on amd64..
I will keep digging, and post any questions in a separate topic.
Thanks for your attention. :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement