All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27904] New: r300g segfaults on M56GL
Date: Thu, 29 Apr 2010 15:25:46 -0700 (PDT)	[thread overview]
Message-ID: <bug-27904-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r300g segfaults on M56GL
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pavel@rojtberg.net


current git, linux 2.6.32-21-generic (ubuntu lucid)

Starting program: /usr/bin/glxgears 
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x004e68e9 in rc_pair_regalloc (c=0xbfffee8c, maxtemps=1)
    at radeon_pair_regalloc.c:347
Line number 347 out of range; radeon_pair_regalloc.c has 280 lines.
(gdb) bt
#0  0x004e68e9 in rc_pair_regalloc (c=0xbfffee8c, maxtemps=1)
    at radeon_pair_regalloc.c:347
#1  0x004e03dd in r3xx_compile_fragment_program (c=0xbfffee8c)
    at r3xx_fragprog.c:159
#2  0x004db6f3 in r300_translate_fragment_shader (r300=<value optimized out>, 
    shader=0x80d0ad8, tokens=0x80ef010) at r300_fs.c:276
#3  0x004dbea7 in r300_pick_fragment_shader (r300=0x8066f08) at r300_fs.c:346
#4  0x004d217f in r300_bind_fs_state (pipe=0x8066f08, shader=0x4e6780)
    at r300_state.c:718
#5  0x00628946 in cso_set_fragment_shader_handle (ctx=0x80e84d8, 
    handle=0x4e6780) at cso_cache/cso_context.c:742
#6  0x005f29e0 in update_fp (st=0x80c3e88)
    at state_tracker/st_atom_shader.c:174
#7  0x005ef9b3 in st_validate_state (st=0x80c3e88)
    at state_tracker/st_atom.c:167
#8  0x005f6859 in st_Clear (ctx=0x8087258, mask=18)
    at state_tracker/st_cb_clear.c:460
#9  0x005a3936 in _mesa_Clear (mask=0) at main/clear.c:178
#10 0x080493d7 in ?? ()
#11 0x0804a762 in ?? ()
#12 0x00305bd6 in __libc_start_main (main=0x804a230, argc=1, 
    ubp_av=0xbffff484, init=0x804ad80, fini=0x804ad70, 
    rtld_fini=0x11e0c0 <_dl_fini>, stack_end=0xbffff47c) at libc-start.c:226

-- 
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-04-29 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 22:25 bugzilla-daemon [this message]
2010-05-01 23:02 ` [Bug 27904] r300g segfaults on M56GL bugzilla-daemon
2010-05-01 23:59 ` bugzilla-daemon
2010-05-02  0:23 ` bugzilla-daemon
2010-05-02  9:51 ` bugzilla-daemon
2010-05-02 10:32 ` 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-27904-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.