dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31569] New: [r300g] SIGSEGV src/mesa/main/api_loopback.c:1470
Date: Thu, 11 Nov 2010 18:21:41 -0800 (PST)	[thread overview]
Message-ID: <bug-31569-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=31569

           Summary: [r300g] SIGSEGV src/mesa/main/api_loopback.c:1470
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: vlee@vmware.com


mesa: d18df9e336b5d2e68a4a6185f7b9d0d0c095c3c4 (master)

chipset: RV530 71C5 (ATI Radeon X1600)
system architecture: i686
libdrm-dev: 2.4.21-1ubuntu2.1
kernel version: 2.6.35-22-generic
Linux distribution: Ubuntu 10.10 i386
Machine model: iMac4,1

Run piglit provoking-vertex test.

$ ./bin/provoking-vertex
radeon: Successfully grabbed chipset info from kernel!
radeon: DRM version: 2.5.0 ID: 0x71c5 GB: 1 Z: 2
radeon: GART size: 509 MB VRAM size: 128 MB
radeon: HyperZ: NO
Mesa: Mesa 7.10-devel DEBUG build Nov 11 2010 12:16:33
Mesa: User error: GL_INVALID_ENUM in vbo_VertexAttribI1ui
Segmentation fault (core dumped)

(gdb) bt
#0  0x017e0d43 in loopback_VertexAttribI1uiv (index=36430, v=0x96) at
src/mesa/main/api_loopback.c:1470
#1  0x0804a5f0 in piglit_display () at
piglit/tests/general/provoking-vertex.c:90
#2  0x0804c6a7 in display () at piglit/tests/util/piglit-framework.c:52
#3  0x006f5820 in fghRedrawWindow (window=0x9c02058, enumerator=0xbfa6e598) at
freeglut_main.c:210
#4  fghcbDisplayWindow (window=0x9c02058, enumerator=0xbfa6e598) at
freeglut_main.c:227
#5  0x006f9660 in fgEnumWindows (enumCallback=0x6f5790 <fghcbDisplayWindow>,
enumerator=0xbfa6e598) at freeglut_structure.c:394
#6  0x006f5cdb in fghDisplayAll () at freeglut_main.c:249
#7  glutMainLoopEvent () at freeglut_main.c:1450
#8  0x006f6605 in glutMainLoop () at freeglut_main.c:1498
#9  0x0804c850 in main (argc=1, argv=0xbfa6e824) at
piglit/tests/util/piglit-framework.c:118
(gdb) frame 0
#0  0x017e0d43 in loopback_VertexAttribI1uiv (index=36430, v=0x96) at
src/mesa/main/api_loopback.c:1470
1470       ATTRIBI_1UI(index, v[0]);
(gdb) l
1465    }
1466    
1467    static void GLAPIENTRY
1468    loopback_VertexAttribI1uiv(GLuint index, const GLuint *v)
1469    {
1470       ATTRIBI_1UI(index, v[0]);
1471    }
1472    
1473    static void GLAPIENTRY
1474    loopback_VertexAttribI4bv(GLuint index, const GLbyte *v)
(gdb) print *v
Cannot access memory at address 0x96

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-11-12  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  2:21 bugzilla-daemon [this message]
2010-11-13 20:24 ` [Bug 31569] [r300g] SIGSEGV src/mesa/main/api_loopback.c:1470 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-31569-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox