From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66349] Using SB shader optimization caused segfault in Serious Sam 3: BFE
Date: Sun, 07 Jul 2013 13:45:28 +0000 [thread overview]
Message-ID: <bug-66349-502-uL5NXAw6Fk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66349-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 601 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66349
--- Comment #8 from Vadim Girlin <ptpzz@yandex.ru> ---
So far I haven't managed to reproduce the issue with the trace, I tried with
32-bit and 64-bit drivers, with and without sb, also I tried to build mesa with
your configure parameters (though I had to adjust them a bit to make it work
for me) - I haven't seen any segfaults with the trace, valgrind doesn't provide
any hints either.
I suspect it may be something specific to your configuration, compiler version,
etc.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1404 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:[~2013-07-07 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 2:10 [Bug 66349] New: Using SB shader optimization caused segfault in Serious Sam 3: BFE bugzilla-daemon
2013-07-03 20:15 ` [Bug 66349] " bugzilla-daemon
2013-07-03 20:49 ` bugzilla-daemon
2013-07-04 18:54 ` bugzilla-daemon
2013-07-05 18:22 ` bugzilla-daemon
2013-07-06 6:41 ` bugzilla-daemon
2013-07-06 12:57 ` bugzilla-daemon
2013-07-06 18:00 ` bugzilla-daemon
2013-07-07 13:45 ` bugzilla-daemon [this message]
2013-07-07 17:57 ` bugzilla-daemon
2019-09-18 19:04 ` 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-66349-502-uL5NXAw6Fk@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