From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37253] SIGSEGV in dri2FlushFrontBuffer/MakeContextCurrent
Date: Tue, 24 May 2011 10:48:14 -0700 (PDT) [thread overview]
Message-ID: <20110524174814.C917E13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37253-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37253
--- Comment #3 from Sven Arvidsson <sa@whiz.se> 2011-05-24 10:48:14 PDT ---
(In reply to comment #2)
> Close the other one as duplicate of this one (despite anachronism) ?
That's probably a good idea. You could also reassign this bug to component
"Mesa core" as it isn't a problem specific to r600g.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-24 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 13:46 [Bug 37253] New: SIGSEGV in dri2FlushFrontBuffer/MakeContextCurrent bugzilla-daemon
2011-05-23 17:12 ` [Bug 37253] " bugzilla-daemon
2011-05-23 23:22 ` bugzilla-daemon
2011-05-24 17:48 ` bugzilla-daemon [this message]
2011-05-24 17:53 ` bugzilla-daemon
2011-05-24 17:53 ` 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=20110524174814.C917E13004E@annarchy.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).