From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 86043] Optimus issue with libdrm 2.4.58 Date: Mon, 02 Mar 2015 09:50:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1952460875==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CCDCB6E41E for ; Mon, 2 Mar 2015 01:50:27 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1952460875== Content-Type: multipart/alternative; boundary="1425289827.FDC372.22955"; charset="UTF-8" --1425289827.FDC372.22955 Date: Mon, 2 Mar 2015 09:50:27 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=86043 --- Comment #9 from Tvrtko Ursulin --- Thanks Emil! Unfortunaltey I am not familiar with Optimus nor do I have appropriate hardware. Could someone provide a backtrace (with symbols) of the binary which ends up saying "malloc: unknown:0: assertion botched", etc? Or maybe even Valgrind it? Although that may be pretty advanced. I don't think this commit is the actual culprit, but it is possible that the failing binary uses UserPtr if it detects it, and has a bug in those optional code paths. Another interesting test would be to try non-working libdrm on a kernel without UserPtr support. -- You are receiving this mail because: You are the assignee for the bug. --1425289827.FDC372.22955 Date: Mon, 2 Mar 2015 09:50:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 9 on bug 86043 from 
Thanks Emil! Unfortunaltey I am not familiar with Optimus nor do I have
appropriate hardware.

Could someone provide a backtrace (with symbols) of the binary which ends up
saying "malloc: unknown:0: assertion botched", etc? Or maybe even Valgrind it?
Although that may be pretty advanced.

I don't think this commit is the actual culprit, but it is possible that the
failing binary uses UserPtr if it detects it, and has a bug in those optional
code paths.

Another interesting test would be to try non-working libdrm on a kernel without
UserPtr support.

You are receiving this mail because:
  • You are the assignee for the bug.
--1425289827.FDC372.22955-- --===============1952460875== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1952460875==--