[Bug 83274] XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 15 10:33:19 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=83274

--- Comment #5 from nicolas <nicolasbugreport at gmail.com> ---
I tried to modify the launch script xcom.sh like this :

if [ -e "$GAMESCRIPT" ]; then
        # Launch the game
        echo "XCOM - Launching"
        valgrind --log-file=valgrindxcom.log "$GAMESCRIPT" $@
    else

The game launch and valgrind makes the log file but i'm not sure that valgrind
works during execution of the game.

here is the output of valgrind, that doesn't seems to help  :

==5476== Memcheck, a memory error detector
==5476== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5476== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==5476== Command:
/home/nicolas/.steam/steam/SteamApps/common/XCom-Enemy-Unknown/binaries/linux/xcom.sh
-arch=x86_64
==5476== Parent PID: 5470
==5476== 
==5477== 
==5477== HEAP SUMMARY:
==5477==     in use at exit: 736,194 bytes in 27 blocks
==5477==   total heap usage: 40 allocs, 13 frees, 998,962 bytes allocated
==5477== 
==5477== LEAK SUMMARY:
==5477==    definitely lost: 0 bytes in 0 blocks
==5477==    indirectly lost: 0 bytes in 0 blocks
==5477==      possibly lost: 0 bytes in 0 blocks
==5477==    still reachable: 736,194 bytes in 27 blocks
==5477==         suppressed: 0 bytes in 0 blocks
==5477== Rerun with --leak-check=full to see details of leaked memory
==5477== 
==5477== For counts of detected and suppressed errors, rerun with: -v
==5477== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==5476== 
==5476== HEAP SUMMARY:
==5476==     in use at exit: 32 bytes in 1 blocks
==5476==   total heap usage: 40 allocs, 39 frees, 998,962 bytes allocated
==5476== 
==5476== LEAK SUMMARY:
==5476==    definitely lost: 0 bytes in 0 blocks
==5476==    indirectly lost: 0 bytes in 0 blocks
==5476==      possibly lost: 0 bytes in 0 blocks
==5476==    still reachable: 32 bytes in 1 blocks
==5476==         suppressed: 0 bytes in 0 blocks
==5476== Rerun with --leak-check=full to see details of leaked memory
==5476== 
==5476== For counts of detected and suppressed errors, rerun with: -v
==5476== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150415/f95d1a84/attachment.html>


More information about the dri-devel mailing list