Jump to content

Running test after building, i get: Function call failed


danto
 Share

Recommended Posts

Hi i'm on linux and i got the source code from gitea.

I run:

libraries/build-source-libs.sh --with-system-nvtt
cd 0ad/build/workspaces
./update-workspaces.sh
cd gcc
make

Everything went ok but then i run the test and i get:

Function call failed: return value was -100101 (Case 1)
Location: tex.cpp:628 (get_data)

If i try to run the game i get a different error

Function call failed: return value was -100032 (Function not supported)
Location: ogg.cpp:240 (Open)

Pics:

Spoiler

image.jpeg.f6c0b7283f8a24872f003e62c5729750.jpeg

Running test.

 

Spoiler

image.jpeg.48ed2d75c28112a870766c9f8623d119.jpeg

Trying to run 0ad.

Can someone help pleeease?

Edited by danto
Link to comment
Share on other sites

 I think there's something to it.

I compile nightly-build using svn under Debian Bookworm according to the recipe:

https://wildfiregames.com/forum/topic/123667-trying-to-compile-0ad-nightly-build-%E2%80%93-debian-bookworm/?do=findComment&comment=583917

At first it was fine, but for a few days now I can't start the game (At revision 51, 52).
After typing './pyrogenesis' a welcome window appears, but after selecting any game the screen goes to a window where nothing can be done and there is information about errors.
The same thing happens in Windows when 'pyrogenesis.exe' is started.

Debian: ./pyrogenesis (final fragment)

GAME STARTED, ALL INIT COMPLETE
Assertion failed: "!!m_Receiver"
Location: Future.h:200 (Get)

Call stack:

(0x55c61253dfde) ./pyrogenesis(+0x88bfde) [0x55c61253dfde]
(0x55c6124e4f6f) ./pyrogenesis(+0x832f6f) [0x55c6124e4f6f]
(0x55c6124e517e) ./pyrogenesis(+0x83317e) [0x55c6124e517e]
(0x55c6124e7171) ./pyrogenesis(+0x835171) [0x55c6124e7171]
(0x55c611eae49e) ./pyrogenesis(+0x1fc49e) [0x55c611eae49e]
(0x55c611dffbdc) ./pyrogenesis(+0x14dbdc) [0x55c611dffbdc]
(0x55c611e0ae5a) ./pyrogenesis(+0x158e5a) [0x55c611e0ae5a]
(0x55c611e5ffdb) ./pyrogenesis(+0x1adfdb) [0x55c611e5ffdb]
(0x55c6120431ec) ./pyrogenesis(+0x3911ec) [0x55c6120431ec]
(0x55c611d85671) ./pyrogenesis(+0xd3671) [0x55c611d85671]
(0x55c611d6d2f8) ./pyrogenesis(+0xbb2f8) [0x55c611d6d2f8]
(0x7f8117d6724a) /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7f8117d6724a]
(0x7f8117d67305) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f8117d67305]
(0x55c611d7ea31) ./pyrogenesis(+0xcca31) [0x55c611d7ea31]

errno = 11 (Try again later)
OS error = ?


Redirecting call to abort() to mozalloc_abort

Segmentation fault

 

cat ../../build/build_version/build_version.txt
L"main, b5d08a" 

grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt
  "build_version": "main, b5d08a",
      "build_version": "2.26.5",
      "build_version": 20100,

 

sed -n '200p' ../../source/ps/Future.h
		ENSURE(!!m_Receiver);

 

md5sum ../../source/ps/Future.h
e490987bb4fa469b609474dd627a6042  ../../source/ps/Future.h
cd /tmp/
wget https://svn.wildfiregames.com/nightly-build/trunk/source/ps/Future.h
md5sum Future.h 
e490987bb4fa469b609474dd627a6042  Future.h

But the 'test' runs fine:

./test 
Running cxxtest tests (413 tests)...OK!

Under Windows the list of errors is longer – see the attached file.

Regards.

 

 

 

Assertion failed !!m_Receiver_52_2024-10-11.txt.zip

Edited by zyli
Link to comment
Share on other sites

Why?

1) Because when using svn, after issuing the command './pyrogenesis' the hash is displayed on the title page: 'b5d08a' (similarly pyrogenesis.exe for Windows).
2) You have 'custom' + compilation date.
3) You write: "now the game runs fine".

4) There is a known bug: https://gitea.wildfiregames.com/0ad/0ad/issues/7103
5) On the page: https://gitea.wildfiregames.com/0ad/0ad the hash 'b5d08a4833' has not changed since 2024-10-09.

Due to the above facts, the currently compiled game should not start correctly (this is not about the game's welcome page).

For me, using svn update (+ subsequent compilation commands) the game cannot be launched under both Debian and Windows (item 4).
On the welcome page I have had the same hash for three days: 'b5d08a'.

That is why I asked this question.

Best regards.

Edited by zyli
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...