Bug 13705 - crash in quad_twoside_unfilled when starting k3dsurf
Summary: crash in quad_twoside_unfilled when starting k3dsurf
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: mesa-dev
QA Contact:
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-17 10:59 UTC by Brice Goglin
Modified: 2018-03-07 04:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Brice Goglin 2007-12-17 10:59:54 UTC
Robin Haunschild and Daniel Blashke and others reported a crash of k3dsurf at startup with mesa 7.0.2 on amd64.

Backtrace below. Let me know if you need more info.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb70c28d0 (LWP 6405)]
0xb6c21bec in quad_twoside_unfilled (ctx=0x8456a00, e0=0, e1=25, e2=26, e3=1) at ../../../../../src/mesa/tnl_dd/t_dd_tritmp.h:447
(gdb) bt full
#0  0xb6c21bec in quad_twoside_unfilled (ctx=0x8456a00, e0=0, e1=25, e2=26, e3=1) at ../../../../../src/mesa/tnl_dd/t_dd_tritmp.h:447
        vbcolor = <value optimized out>
        mode = 6913
        coloroffset = 3
        specoffset = 0 '\0'
#1  0xb6cb0d5a in _tnl_render_quads_elts (ctx=0x8456a00, start=0, count=2304, flags=55) at tnl/t_vb_rendertmp.h:334
        j = 7
        tnl = (TNLcontext *) 0x8494008
        elt = (const GLuint * const) 0xb0b0c008
        QuadFunc = (const tnl_quad_func) 0xb6c21950 <quad_twoside_unfilled>
        stipple = 0 '\0'
#2  0xb6cb1146 in run_render (ctx=0x8456a00, stage=0x849424c) at tnl/t_vb_render.c:320
        prim = 0
        start = 0
        length = <value optimized out>
        i = 0
        tnl = (TNLcontext *) 0x8494008
        tab = (tnl_render_func *) 0xb6ddaa00
        pass = 0
        __PRETTY_FUNCTION__ = "run_render"
#3  0xb6ca85e3 in _tnl_run_pipeline (ctx=0x8456a00) at tnl/t_pipeline.c:158
        tnl = (TNLcontext *) 0x8494008
        __tmp = 895
        i = 10
        mask = 63
#4  0xb6c16c87 in intelRunPipeline (ctx=0x8456a00) at intel_tris.c:764
No locals.
#5  0xb6ca8b61 in _tnl_draw_prims (ctx=0x8456a00, arrays=0x8482748,  prim=0xbfbcef20, nr_prims=1, ib=0xbfbcef10, min_index=0, max_index=624) at tnl/t_draw.c:402
        bo = {0xbfbcef18, 0xb6bfcb5f, 0x8456a00, 0xb6dd9640, 0xbfbcee78, 
  0xb6c9ced9, 0x8456a00, 0x4400, 0xbfbcef50, 0xb7f74668, 0x8050299, 
  0xb6dd9640, 0xbfbcee98, 0xb6c9cb38, 0x8456a00, 0x4400, 0xbfbcee98, 
  0xb6c9cff7, 0x8456a00, 0xb6cbdc08, 0xbfbceeb8, 0xb6bff91c, 0x8456a00, 
  0x845761c, 0x8456a00, 0xb6dd9640, 0x8480730, 0x8480e70, 0xbfbceed8, 
  0xb6c9dd90, 0x1, 0x4400, 0x8456a00}
        nr_bo = 0
        tnl = (TNLcontext *) 0x8494008
#6  0xb6ca1166 in vbo_exec_DrawRangeElements (mode=7, start=0, end=624,  count=2304, type=5125, indices=0xb0b0c008) at vbo/vbo_exec_array.c:330
        ctx = <value optimized out>
        ib = {count = 2304, type = 5125, obj = 0x8432158, ptr = 0xb0b0c008}
        prim = {{mode = 7, indexed = 1, begin = 1, end = 1, weak = 0, pad = 0, 
    start = 0, count = 2304}}
#7  0xb6ca1372 in vbo_exec_DrawElements (mode=7, count=2304, type=5125, indices=0xb0b0c008) at vbo/vbo_exec_array.c:359
        min_index = 0
        max_index = 624
#8  0x080baabf in ?? ()
No symbol table info available.
#9  0x080c0a17 in ?? ()
No symbol table info available.
#10 0xb7cec1b9 in QGLWidget::glDraw () from /usr/lib/libqt-mt.so.3
No symbol table info available.
#11 0xb7ceb8be in QGLWidget::updateGL () from /usr/lib/libqt-mt.so.3
No symbol table info available.
#12 0x080ee91a in ?? ()
No symbol table info available.
#13 0x0805484d in ?? ()
No symbol table info available.
#14 0xb72ca450 in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#15 0x080546b1 in ?? ()
No symbol table info available.
(gdb)
Comment 1 Timothy Arceri 2018-03-07 04:43:05 UTC
This function doesn't seem to exist in modern mesa. Closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.