Re: progress
Code:
22:47:30 L 10/26/2017 - 17:46:58: [META] WARNING: dll: Failed query plugin '<sandbot.so>'; Couldn't open file '/home/desktop/steamcmd/hlds/gearbox/dlls/sandbot.so': /home/desktop/steamcmd/hlds/gearbox/dlls/sandbot.so: undefined symbol: _ZdlPvj |
Re: progress
Ah sorry - try v0.4 I think (https://github.com/tschumann/sandbot...9648020d59f84f was when I updated to Visual Studio 2017 and Ubuntu 17 was not long after; https://github.com/tschumann/sandbot...b53c919c8fdd15 was v0.4).
|
Re: progress
I've loaded v0.4 on my Op4CTF server with using GDB Debug mode with Metamod 1.21-p37 and this is what I got:-
Code:
Program received signal SIGSEGV, Segmentation fault. Code:
(gdb) bt |
Re: progress
Hm, I'll see what I can figure out - nothing obvious looking at the code but I don't think I regression tested the waypoint stuff on Linux so it looks like there probably is a bug.
I might not get to it this weekend but I'll see what I can do. |
Re: progress
Okay, it looks like you're running from HLDS rather than Steam itself? I've been looking into debugging with Steam and it looks like a mess. Looks like it worked at one point (http://steamcommunity.com/app/221410...3757387624740/) but GAME_DEBUGGER is no longer in steam.sh, so that's no good. On the plus side Steam seems to generate minidumps regardless of OS settings but of course gdb can't load minidumps. There's a tool called minidump-2-core that's part of google-breakpad but it's not in any mirror that I can find, so my only option is to clone and build (which I'd like to avoid).
How easy is it to set up HLDS, get it running and generate a crash dump? Also, I got a similar crash to you with v0.4.1 (couldn't find Bot::GetSkill) which I fixed with https://github.com/tschumann/sandbot...e2d34c45245bf2 - I don't know a whole lot about C++ constructors etc but it seems to work fine on Windows. Possibly a gcc flag? |
Re: progress
Also, does v0.4.1 work for Half-Life on Ubuntu 14.04?
|
Re: progress
For HLDM without Metamod yes - With Metamod no. I don't know why it crashes and the GDB gave me a huge list of errors linked to metamod.so - even without the other Addons like AMXX and Spawn & Chat Protection.
Code:
Program received signal SIGBUS, Bus error. I don't know much on how you code for Sandbot, but is it possible that those bots only work if the builds were split to do only load as a Standalone and as a Metamod build? E.g sandbot.dll and sandbot.so for Standalone and sandbot_mm.dll and sandbot_mm.so for Metamod? |
Re: progress
@RoboCop The list is are watching is just a backtrace, not a "huge list of errors". There is no really a reason to split the builds for Metamod and Non-Metamod. The code is isolated in checks and calls Metamod functions when loaded as plugin and the normal game/engine functions when is working standalone.
|
Re: progress
Quote:
Quote:
I suspect the issue is to do with sub-classing or how it is built on Linux as it works on Windows (though it's possible I'm invoking undefined behaviour and Visual Studio generates better code for the situation). Looks like there could be a problem with the waypoint code on Linux too though I haven't really touched that, so not sure what it could be. I'll try and sort out the Opposing Force crash first anyway. If anyone knows how to get Half-Life to generate gdb core dumps that would help too. |
Re: progress
Quote:
Then type this in Terminal but don't use "./hlds_run", use "run -game gearbox -ip xx.xx.xx.xx +port 27015 +map op4_bootcamp +exec server.cfg -debug" You can backtrace or get a full error crash log by typing "bt" as well rerunning the server using "run" (Nothing further as GDB stored the Startup Variables once after GDB is exited by typing "quit") And "How about v0.4?" you say? Well I just did the tests and they don't seem to instantly crash as much as v0.4.1 did... |
All times are GMT +2. The time now is 06:37. |
Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.