From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36037] RV250Lf: airlied/drm-fixes branch crashes in new backlight code
Date: Thu, 7 Apr 2011 08:35:56 -0700 (PDT) [thread overview]
Message-ID: <20110407153556.F382C13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36037-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36037
--- Comment #5 from Michel Dänzer <michel@daenzer.net> 2011-04-07 08:35:56 PDT ---
Created an attachment (id=45386)
View: https://bugs.freedesktop.org/attachment.cgi?id=45386
Review: https://bugs.freedesktop.org/review?bug=36037&attachment=45386
Debugging patch
This patch (only compile tested) should print the pointer values before
referencing them, and bail if one of them is NULL. This should also avoid the
immediate crash, but it might still crash elsewhere later on.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-04-07 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-36037-502@http.bugs.freedesktop.org/>
2011-04-07 9:58 ` [Bug 36037] RV250Lf: airlied/drm-fixes branch crashes in new backlight code bugzilla-daemon
2011-04-07 14:27 ` bugzilla-daemon
2011-04-07 14:51 ` bugzilla-daemon
2011-04-07 15:35 ` bugzilla-daemon [this message]
2011-04-07 17:03 ` bugzilla-daemon
2011-04-07 18:00 ` bugzilla-daemon
2011-04-14 14:59 ` bugzilla-daemon
2011-04-14 15:29 ` bugzilla-daemon
2012-01-04 13:06 ` 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=20110407153556.F382C13004F@annarchy.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