All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83274] XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602
Date: Wed, 15 Apr 2015 03:25:06 +0000	[thread overview]
Message-ID: <bug-83274-502-RDhGecCRnw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83274-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 573 bytes --]

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

--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
(In reply to nicolas from comment #3)
> Can you explain me what parameters i have to use with valgrind  ( i have
> installed it) so that it can makes a useful output for you?

For a start, just prepend valgrind to the final command line invoked for
starting the game. I don't know offhand how to do that for XCOM, hopefully
someone else can help you with that if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1486 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-04-15  3:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 14:05 [Bug 83274] New: XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602 bugzilla-daemon
2014-09-01  1:30 ` [Bug 83274] " bugzilla-daemon
2015-04-14 20:31 ` bugzilla-daemon
2015-04-14 20:36 ` bugzilla-daemon
2015-04-15  3:25 ` bugzilla-daemon [this message]
2015-04-15 17:33 ` bugzilla-daemon
2015-04-16  1:29 ` bugzilla-daemon
2015-04-16  6:56 ` bugzilla-daemon
2015-04-17 17:04 ` bugzilla-daemon
2019-09-18 19:17 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-83274-502-RDhGecCRnw@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.