From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98170] [vdpau] Error when calling vdp_output_surface_create
Date: Tue, 11 Oct 2016 12:20:40 +0000 [thread overview]
Message-ID: <bug-98170-502-OH1bvThFsJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98170-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 875 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98170
--- Comment #3 from Christian König <deathsimple@vodafone.de> ---
Bisecting means you try to figure out what patch introduced this bug.
E.g. you know that 11.2.2 work and 12.0.1 is broken. So you checkout the source
code from git and issue "git bisect start mesa-12.0.1 mesa-11.2.2".
Now git has the list of changes between 11.2.2 and 12.0.1, so it jumps into the
middle of that list of changes.
You then compile mesa and see if this version still works.
If it works you say "git bisect good" and git will jump another quarter to the
end of the list, if it doesn't work you say "git bisect bad" and git will jump
a quarter to the beginning of the list.
This repeats until you figured out which commit caused the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1700 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
next prev parent reply other threads:[~2016-10-11 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 13:03 [Bug 98170] [vdpau] Error when calling vdp_output_surface_create bugzilla-daemon
2016-10-11 7:26 ` bugzilla-daemon
2016-10-11 9:00 ` bugzilla-daemon
2016-10-11 12:20 ` bugzilla-daemon [this message]
2016-10-23 8:05 ` bugzilla-daemon
2016-10-24 9:01 ` bugzilla-daemon
2016-10-24 10:58 ` bugzilla-daemon
2016-10-27 9:22 ` bugzilla-daemon
2016-11-14 16:21 ` bugzilla-daemon
2016-11-14 16:22 ` 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-98170-502-OH1bvThFsJ@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;
as well as URLs for NNTP newsgroup(s).