From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27148] New: Failed assertion in piglit test 'bin/fbo-flushing -auto' with RV790
Date: Wed, 17 Mar 2010 15:51:37 -0700 (PDT) [thread overview]
Message-ID: <bug-27148-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=27148
Summary: Failed assertion in piglit test 'bin/fbo-flushing -auto'
with RV790
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: rankincj@googlemail.com
fbo-flushing: /home/chris/Programs/piglit/tests/fbo/fbo-flushing.c:79:
piglit_display: Assertion `__glewCheckFramebufferStatusEXT(0x8D40) == 0x8CD5'
failed.
Aborted (core dumped)
Core was generated by `bin/fbo-flushing -auto'.
Program terminated with signal 6, Aborted.
#0 0x00000039638326c5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-8.fc12.x86_64
glew-1.5.1-3.fc12.x86_64 glibc-2.11.1-1.x86_64 libICE-1.0.6-1.fc12.x86_64
libSM-1.1.0-7.fc12.x86_64 libX11-1.3-1.fc12.x86_64 libXau-1.0.5-1.fc12.x86_64
libXdamage-1.1.2-1.fc12.x86_64 libXext-1.1-2.fc12.x86_64
libXfixes-4.0.4-1.fc12.x86_64 libXi-1.3-2.fc12.x86_64
libXmu-1.0.5-1.fc12.x86_64 libXt-1.0.7-1.fc12.x86_64
libXxf86vm-1.1.0-1.fc12.x86_64 libdrm-2.4.18-0.1.fc12.x86_64
libgcc-4.4.3-4.fc12.x86_64 libjpeg-6b-46.fc12.x86_64
libstdc++-4.4.3-4.fc12.x86_64 libtiff-3.9.2-3.fc12.x86_64
libuuid-2.16.2-7.fc12.x86_64 libxcb-1.5-1.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) where
#0 0x00000039638326c5 in raise () from /lib64/libc.so.6
#1 0x0000003963833ea5 in abort () from /lib64/libc.so.6
#2 0x000000396382b7b5 in __assert_fail () from /lib64/libc.so.6
#3 0x0000000000402950 in piglit_display ()
at /home/chris/Programs/piglit/tests/fbo/fbo-flushing.c:78
#4 0x0000000000403fb9 in display ()
at /home/chris/Programs/piglit/tests/util/piglit-framework.c:44
#5 0x00007fa56dc583bb in processWindowWorkList (window=0x2296310)
at glut_event.c:1307
#6 0x00007fa56dc59224 in __glutProcessWindowWorkLists () at glut_event.c:1358
#7 glutMainLoop () at glut_event.c:1379
#8 0x0000000000404149 in main (argc=1, argv=0x7fffadb4ad18)
at /home/chris/Programs/piglit/tests/util/piglit-framework.c:94
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-17 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 22:51 bugzilla-daemon [this message]
2010-03-18 20:18 ` [Bug 27148] Failed assertion in piglit test 'bin/fbo-flushing -auto' with RV790 bugzilla-daemon
2010-03-26 10:34 ` bugzilla-daemon
2012-09-11 9:50 ` 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-27148-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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.