All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43522] New: matrixview segfaults because of _tnl_emit_vertices_to_buffer heap corruption
Date: Sun, 04 Dec 2011 21:49:54 +0000	[thread overview]
Message-ID: <bug-43522-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 43522
           Summary: matrixview segfaults because of
                    _tnl_emit_vertices_to_buffer heap corruption
    Classification: Unclassified
           Product: Mesa
           Version: 7.11
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/Savage
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: bugzi11.fdo.tormod@xoxy.net


Created attachment 54114
  --> https://bugs.freedesktop.org/attachment.cgi?id=54114
gdb session with backtrace from corruption

The matrixview screensaver hack from rss-glx (Really Slick Screensavers Port to
GLX) segfaults very reproducibly on my savage laptop. The
_swrast_context->InvalidateState function pointer gets overwritten and
_swrast_InvalidateState segfaults.

I have tracked this down to emit_viewport4_bgra4_st2() from
src/mesa/tnl/t_vertex_generic.c (see attached gdb session).

This happens with or without MESA_NO_CODEGEN=1 but gdb made more sense with it.

-- 
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:[~2011-12-04 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-43522-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.