From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 86356] [nv50] Graphical glitches in dota2
Date: Sun, 16 Nov 2014 23:14:30 +0000 [thread overview]
Message-ID: <bug-86356-8800-svNuNWf9Qa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86356-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86356
--- Comment #3 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
The following messages while replaying the trace are due to the trimming:
Mesa: User error: GL_INVALID_OPERATION in glDeleteShader
XX: glDebugOutputCallback: High severity API error 2, GL_INVALID_OPERATION in
glDeleteShader
0 XX glDeleteShader(shader = YY)
Running against debug mesa (./configure --enable-debug ...) does not trigger
any asserts or produce extra output to stderr/stdout.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1322 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-11-16 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 21:46 [Bug 86356] New: [nv50] Graphical glitches in dota2 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-86356-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-11-16 21:48 ` [Bug 86356] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-16 21:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-16 21:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-16 23:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-06-28 6:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-86356-8800-svNuNWf9Qa@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.