From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57977] Crash after multiple resolution change
Date: Fri, 07 Dec 2012 15:47:35 +0000 [thread overview]
Message-ID: <bug-57977-502-Nm2tyzPElK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57977-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 796 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=57977
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #5 from Michel Dänzer <michel@daenzer.net> ---
According to the valgrind output, the supertuxkart / irrlicht code is writing
to some memory after freeing it, which could explain the problem. I think you
should take this back up with the supertuxkart developers. Feel free to reopen
if the problem persists after fixing those invalid writes.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2279 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
prev parent reply other threads:[~2012-12-07 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 8:44 [Bug 57977] New: Crash after multiple resolution change bugzilla-daemon
2012-12-07 9:23 ` [Bug 57977] " bugzilla-daemon
2012-12-07 9:56 ` bugzilla-daemon
2012-12-07 9:59 ` bugzilla-daemon
2012-12-07 13:58 ` bugzilla-daemon
2012-12-07 14:00 ` bugzilla-daemon
2012-12-07 15:47 ` bugzilla-daemon [this message]
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-57977-502-Nm2tyzPElK@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