From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75061] bug in clearing color buffer
Date: Mon, 24 Feb 2014 12:36:17 +0000 [thread overview]
Message-ID: <bug-75061-502-224R31wG0u@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75061-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75061
--- Comment #13 from Marek Olšák <maraeo@gmail.com> ---
If the program called MapBufferRange(MAP_INVALIDATE_BUFFER_BIT) instead of
BufferData, I think it would be okay to crash:
>From GL 4.4 spec:
"MAP_INVALIDATE_BUFFER_BIT indicates that the previous contents of the entire
buffer may be discarded. Data within the entire buffer are undefined with the
exception of subsequently written data. No GL error is generated if subsequent
GL operations access unwritten data, but the result is undefined and system
errors (possibly including program termination) may occur."
In other words, no context should access the buffer until UnmapBuffer() is
complete, because there may be unwritten data.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1603 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:[~2014-02-24 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-75061-502@http.bugs.freedesktop.org/>
2014-02-24 7:04 ` [Bug 75061] bug in clearing color buffer bugzilla-daemon
2014-02-24 12:04 ` bugzilla-daemon
2014-02-24 12:36 ` bugzilla-daemon [this message]
2014-03-08 22:39 ` bugzilla-daemon
2014-03-08 22:57 ` bugzilla-daemon
2014-09-17 23:27 ` bugzilla-daemon
2017-03-22 15:24 ` bugzilla-daemon
2019-09-18 19: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-75061-502-224R31wG0u@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).