<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Optimus issue with libdrm 2.4.58" href="https://bugs.freedesktop.org/show_bug.cgi?id=86043#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Optimus issue with libdrm 2.4.58" href="https://bugs.freedesktop.org/show_bug.cgi?id=86043">bug 86043</a> from <a class="email" href="mailto:tvrtko.ursulin@linux.intel.com" title="Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>"> Tvrtko Ursulin</a> <pre>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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>