From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 74539] [r600g] Memory leak when playing WoW with RV790 Date: Mon, 03 Mar 2014 21:54:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0839968588==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 72ABF10579E for ; Mon, 3 Mar 2014 13:54:21 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0839968588== Content-Type: multipart/alternative; boundary="1393883661.528e6D20.31617"; charset="us-ascii" --1393883661.528e6D20.31617 Date: Mon, 3 Mar 2014 21:54:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=74539 --- Comment #9 from Chris Rankin --- Has anyone ever "valground" a 32 bit executable on a box which is natively 64 bit, please? This bug is currently making it impossible to run Wow-64.exe: http://bugs.winehq.org/show_bug.cgi?id=35582 That in itself isn't an issue - the memory leak occurs with both 32 bit and 64 bit WoW. However, the following command is failing: $ valgrind --trace-children=yes --leak-check=full /usr/bin/wine /opt/wine/World\ of\ Warcraft/Wow.exe -opengl -noautoload64bit with this error: valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No such file or directory Which I assume means that Valgrind is trying to use 64 bit tools on a 32 bit executable. -- You are receiving this mail because: You are the assignee for the bug. --1393883661.528e6D20.31617 Date: Mon, 3 Mar 2014 21:54:21 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 9 on bug 74539 from 
Has anyone ever "valground" a 32 bit executable on a box which is natively 64
bit, please? This bug is currently making it impossible to run Wow-64.exe:

http://bugs.winehq.org/show_bug.cgi?id=35582

That in itself isn't an issue - the memory leak occurs with both 32 bit and 64
bit WoW. However, the following command is failing:

$ valgrind --trace-children=yes --leak-check=full /usr/bin/wine
/opt/wine/World\ of\ Warcraft/Wow.exe -opengl -noautoload64bit

with this error:

valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No such
file or directory

Which I assume means that Valgrind is trying to use 64 bit tools on a 32 bit
executable.

You are receiving this mail because:
  • You are the assignee for the bug.
--1393883661.528e6D20.31617-- --===============0839968588== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0839968588==--