Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

Crash dump

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • <><
    replied
    You should post this to the official linux / os x bug tracker: https://github.com/ValveSoftware/Dota-2/issues to ensure that your issue gets the devs attention.

    Leave a comment:


  • Aphid
    started a topic Crash dump

    Crash dump

    Linux bugtracker post related to this issue: https://github.com/ValveSoftware/Dota-2/issues/540

    A custom game managed to crash the dota 2 client completely in a certain situation.

    This dump file may be valuable.

    Game in question is THD2. Apparently the crash does not consistently happen on all machines. At least using the Linux dota build it does.
    To reproduce the crash, pick Koishi/Sniper and get to level 6, then press R. On my machine dota 2 unceremoniously CTD's.

    I haven't been able to figure out exactly what library tricks are being pulled by Steam internally and can't launch dota 2 from cmdline / using gdb yet to look further. Maybe someone else can do this.

    assert_20151007171802_63.dmp.zip

    Edit: I've tried attaching 'gdb' to dota while in this mode solo. Unfortunately it won't work out of the box -- there's some anti-debugging obfuscation in the game that causes it to detect a vanilla debugger and autolose the game. Which means I can't really see what's going on like this. Is there any flags or such I can set to turn this off? EDIT: Setting 'cheats' on solves it apparently.

    There's one interesting thing I observed; the hero model corrupted itself while the debugger was attached when using this ability. Seems like some textures got stretched out / warped -- the hero model textures stretch out past the edge of the screen and flicker, the screen looks like a green-and-yellow white noise for a bit. Then the game did NOT crash, but seems to keep working fine. The issue might be related to a graphical error.

    Here's some debug output from when the issue happens. Note that when I force a 'continue' upon receiving the SIGTRAP, dota will continue to work. (However, the graphical glitch described above happens for a brief period of time (0.5s or so)).

    Code:
    Reading symbols from /ssd3/home/aphid/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libidn.so.11...(no debugging symbols found)...done.
    Reading symbols from /usr/lib/libseccomp.so.2...(no debugging symbols found)...done.
    Reading symbols from /ssd3/home/aphid/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libattr.so.1...(no debugging symbols found)...done.
    0x00007f8508c7391d in nanosleep () from /usr/lib/libc.so.6
    (gdb) continue
    Continuing.
    
    Program received signal SIGTRAP, Trace/breakpoint trap.
    [Switching to Thread 0x7f84ff5ff700 (LWP 5678)]
    0x00007f84fb299491 in ?? () from /ssd1/steamlib_1/steamapps/common/dota 2 beta/game/bin/linuxsteamrt64/librendersystemgl.so
    (gdb) continue
    Continuing.
    
    Program received signal SIGTRAP, Trace/breakpoint trap.
    [Switching to Thread 0x7f84ffe00700 (LWP 5677)]
    0x00007f84fb299491 in ?? () from /ssd1/steamlib_1/steamapps/common/dota 2 beta/game/bin/linuxsteamrt64/librendersystemgl.so
    (gdb) continue
    Continuing.
    
    Program received signal SIGTRAP, Trace/breakpoint trap.
    [Switching to Thread 0x7f84ff5ff700 (LWP 5678)]
    0x00007f84fb299491 in ?? () from /ssd1/steamlib_1/steamapps/common/dota 2 beta/game/bin/linuxsteamrt64/librendersystemgl.so
    (gdb) continue
    Continuing.
    [New Thread 0x7f84d8c19700 (LWP 5758)]
    [New Thread 0x7f84d8b18700 (LWP 5759)]
    Last edited by Aphid; 10-08-2015, 12:03 AM. Reason: Add link to linux tracker.
Working...
X