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: Tue, 14 Apr 2015 20:31:33 +0000 [thread overview]
Message-ID: <bug-83274-502-WLzq4VVLOL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83274-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 438 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83274
--- Comment #2 from nicolas <nicolasbugreport@gmail.com> ---
(In reply to Michel Dänzer from comment #1)
> Looks like memory corruption. If it's not bug 80673 (which is supposed to be
> fixed in the latest game update), can you attach the output from running the
> game in valgrind?
Hie,
i h
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1553 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
next prev parent reply other threads:[~2015-04-14 20:31 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 [this message]
2015-04-14 20:36 ` bugzilla-daemon
2015-04-15 3:25 ` bugzilla-daemon
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-WLzq4VVLOL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox