All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN
Date: Thu, 07 Jul 2016 07:50:38 +0000	[thread overview]
Message-ID: <bug-96678-502-wxCO9YEmem@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96678-502@http.bugs.freedesktop.org/>


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

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

--- Comment #20 from Michel Dänzer <michel@daenzer.net> ---
Presumably it works with valgrind because it prevents the fatal effect of the
bad memory access which causes the problem. Note that valgrind stopped logging
errors after 1000 instances of the same (presumably harmless) issue in the
Awesomenauts code. Maybe there's some way to suppress those, so we can see the
problem?

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

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

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

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

  parent reply	other threads:[~2016-07-07  7:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26  1:46 [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN bugzilla-daemon
2016-07-01 13:13 ` bugzilla-daemon
2016-07-04  2:33 ` bugzilla-daemon
2016-07-04  2:34 ` bugzilla-daemon
2016-07-04  2:50 ` bugzilla-daemon
2016-07-04  2:51 ` bugzilla-daemon
2016-07-04 10:16 ` bugzilla-daemon
2016-07-04 16:00 ` bugzilla-daemon
2016-07-05  2:03 ` bugzilla-daemon
2016-07-06  9:21 ` bugzilla-daemon
2016-07-06  9:42 ` bugzilla-daemon
2016-07-06 10:43 ` bugzilla-daemon
2016-07-06 10:46 ` bugzilla-daemon
2016-07-06 12:16 ` bugzilla-daemon
2016-07-06 12:45 ` bugzilla-daemon
2016-07-06 12:50 ` bugzilla-daemon
2016-07-06 13:01 ` bugzilla-daemon
2016-07-07  3:06 ` bugzilla-daemon
2016-07-07  6:51 ` bugzilla-daemon
2016-07-07  6:54 ` bugzilla-daemon
2016-07-07  7:50 ` bugzilla-daemon [this message]
2016-07-07  9:44 ` bugzilla-daemon
2016-07-07 13:03 ` bugzilla-daemon
2016-07-07 13:29 ` bugzilla-daemon
2016-07-13  9:26 ` bugzilla-daemon
2016-07-23 11:16 ` bugzilla-daemon
2016-07-23 11:31 ` bugzilla-daemon
2016-10-26 10:51 ` bugzilla-daemon
2016-10-27  5:47 ` bugzilla-daemon
2016-11-04 10:15 ` 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-96678-502-wxCO9YEmem@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.