1. We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Disable all Lua Add-Ons by using '/lua unload' in local chat or temporarily move all files/folders out of the SotA Lua folder then restart the game.
      Ensure the issue still occurs before submitting a bug; Support staff will not debug Add-On issues
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

SEGV under Linux/Steam

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by Zoe, Apr 12, 2019.

  1. Zoe

    Zoe Avatar

    Likes Received:
    Trophy Points:
    I've been playing for the last week or two, via Steam, offline only; a short while ago I found Brittany for the first time, and attempted to enter the Graveyard; at the point the game crashed, leaving a core dump. This is a Ubuntu system that describes itself as:
    % uname -a
    Linux shad2 3.13.0-167-generic #217-Ubuntu SMP Wed Mar 13 16:18:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

    At the point it crashed there was also a pending new game update, which Steam immediately started to download; after that completed I attempted to enter the game again, but it crashed while trying to load.

    The core dump appears to be truncated:
    % file core
    core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), too many program headers (831)
    % gdb ./Shroud\ of\ the\ Avatar.x86_64 core
    Reading symbols from ./Shroud of the Avatar.x86_64...(no debugging symbols found)...done.
    BFD: Warning: /src/steam/steam/steamapps/common/SotA/core is truncated: expected core file size >= 5353394176, found: 104857600.

    warning: core file may not match specified executable file.
    [New LWP 16002]
    ... 43 similar lines
    Cannot access memory at address 0x7fc5db5c91a8
    Cannot access memory at address 0x7fc5db5c91a0
    (gdb) where
    Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x7fc5db4016b0:
    #0 0x00007fc5db3b83e0 in ?? ()
    Cannot access memory at address 0x7fc5db4016b0

    Going back to the last save has worked ok, so I'm back at Yew; I'll update later to advise whether this repeats when I get back to Brittany once more.

  2. Zoe

    Zoe Avatar

    Likes Received:
    Trophy Points:
    Going back there from Yew it did _not_ crash, so I'm back up and running.

    Please advise if for future crashes it would be useful to get a stacktrace or other info from gdb: if it would, I'll try to increase the maximum core dump size.