From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73504] New: Segfault in _save_Normal3fv running FlightGear
Date: Sat, 11 Jan 2014 17:26:06 +0000 [thread overview]
Message-ID: <bug-73504-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4363 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73504
Priority: medium
Bug ID: 73504
Assignee: dri-devel@lists.freedesktop.org
Summary: Segfault in _save_Normal3fv running FlightGear
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: nine@detonation.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 91869
--> https://bugs.freedesktop.org/attachment.cgi?id=91869&action=edit
full konsole output of a session with a crash
Running latest FlightGear git version on openSUSE 13.1 with
Mesa-10.1~git20140110-1.1.x86_64, libLLVM35-3.5~svn20140107-1.1.x86_64,
llvm-r600-3.5~svn20140107-1.1.x86_64, libdrm2-2.4.99~git20131225-1.2.x86_64 and
kernel 3.13.0-rc7-6.g57a2f1c-desktop on a Radeon HD 5670 I get segfaults at
seemingly random points. The backtrace always looks like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffebb61700 (LWP 10909)]
0x00007fffee1d5d23 in _save_Normal3fv (v=0x0) at vbo/vbo_attrib_tmp.h:340
340 vbo/vbo_attrib_tmp.h: No such file or directory.
(gdb) bt
#0 0x00007fffee1d5d23 in _save_Normal3fv (v=0x0) at vbo/vbo_attrib_tmp.h:340
#1 0x00007fffee0df589 in _ae_ArrayElement (elt=0) at main/api_arrayelt.c:1714
#2 0x00007fffee1cf690 in _save_OBE_DrawArrays (mode=<optimized out>,
start=<optimized out>, count=<optimized out>) at vbo/vbo_save_api.c:1103
#3 0x00007ffff52ea0ed in osg::DrawArrays::draw(osg::State&, bool) const ()
from /opt/FlightGear/lib64/libosg.so.100
#4 0x00007ffff52341fa in osg::Geometry::drawImplementation(osg::RenderInfo&)
const () from /opt/FlightGear/lib64/libosg.so.100
#5 0x00007ffff68b8780 in osg::Drawable::draw(osg::RenderInfo&) const () from
/opt/FlightGear/lib64/libosgParticle.so.100
#6 0x00007ffff623ea98 in osgUtil::RenderLeaf::render(osg::RenderInfo&,
osgUtil::RenderLeaf*) () from /opt/FlightGear/lib64/libosgUtil.so.100
#7 0x00007ffff623312c in
osgUtil::RenderBin::drawImplementation(osg::RenderInfo&, osgUtil::RenderLeaf*&)
() from /opt/FlightGear/lib64/libosgUtil.so.100
#8 0x00007ffff6232f2b in osgUtil::RenderBin::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#9 0x00007ffff6233436 in
osgUtil::RenderBin::drawImplementation(osg::RenderInfo&, osgUtil::RenderLeaf*&)
() from /opt/FlightGear/lib64/libosgUtil.so.100
#10 0x00007ffff6244c13 in
osgUtil::RenderStage::drawImplementation(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#11 0x00007ffff6232f2b in osgUtil::RenderBin::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#12 0x00007ffff624352a in osgUtil::RenderStage::drawInner(osg::RenderInfo&,
osgUtil::RenderLeaf*&, bool&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#13 0x00007ffff624446e in osgUtil::RenderStage::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#14 0x00007ffff6253e4e in osgUtil::SceneView::draw() () from
/opt/FlightGear/lib64/libosgUtil.so.100
#15 0x00007ffff5b02a14 in osgViewer::Renderer::draw() () from
/opt/FlightGear/lib64/libosgViewer.so.100
#16 0x00007ffff5b03c2a in
osgViewer::Renderer::operator()(osg::GraphicsContext*) () from
/opt/FlightGear/lib64/libosgViewer.so.100
#17 0x00007ffff52698e1 in osg::GraphicsContext::runOperations() () from
/opt/FlightGear/lib64/libosg.so.100
#18 0x00007ffff52740c9 in osg::RunOperations::operator()(osg::GraphicsContext*)
() from /opt/FlightGear/lib64/libosg.so.100
#19 0x00007ffff5273a38 in osg::GraphicsOperation::operator()(osg::Object*) ()
from /opt/FlightGear/lib64/libosg.so.100
#20 0x00007ffff52dec8f in osg::OperationThread::run() () from
/opt/FlightGear/lib64/libosg.so.100
#21 0x00007ffff527399e in osg::GraphicsThread::run() () from
/opt/FlightGear/lib64/libosg.so.100
#22 0x00007ffff4c52bfc in OpenThreads::ThreadPrivateActions::StartThread(void*)
() from /opt/FlightGear/lib64/libOpenThreads.so.13
#23 0x00007ffff77260db in start_thread () from /lib64/libpthread.so.0
#24 0x00007ffff206090d in clone () from /lib64/libc.so.6
Is this a bug in Mesa or more probably in FlightGear?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5940 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 reply other threads:[~2014-01-11 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 17:26 bugzilla-daemon [this message]
2014-01-24 14:19 ` [Bug 73504] Segfault in _save_Normal3fv running FlightGear bugzilla-daemon
2014-01-24 14:20 ` bugzilla-daemon
2014-01-24 14:21 ` bugzilla-daemon
2014-01-27 22:11 ` bugzilla-daemon
2014-02-04 22:18 ` bugzilla-daemon
2014-02-04 22:20 ` bugzilla-daemon
2014-02-13 21:56 ` bugzilla-daemon
2014-02-27 21:38 ` bugzilla-daemon
2014-02-28 0:17 ` bugzilla-daemon
2019-09-18 19:12 ` 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-73504-502@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 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.