<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault in xf86DestroyI2CDevRec"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93675#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault in xf86DestroyI2CDevRec"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93675">bug 93675</a>
from <span class="vcard"><a class="email" href="mailto:elyk03@gmail.com" title="Kyle Guinn <elyk03@gmail.com>"> <span class="fn">Kyle Guinn</span></a>
</span></b>
<pre>(In reply to Kevin Brace from <a href="show_bug.cgi?id=93675#c8">comment #8</a>)
<span class="quote">> If you take out xf86DestroyI2CDevRec API call after 2 calls to
> xf86I2CProbeAddress API call, the problem seems to go away (I am not sure if
> this is okay. If it is not, let me know.).
>
> _____________________________________________________________________________
>
> if (xf86I2CProbeAddress(pVia->pI2CBus3, pDev->SlaveAddr)) {
> pDev->pI2CBus = pVia->pI2CBus3;
> } else if (xf86I2CProbeAddress(pVia->pI2CBus2, pDev->SlaveAddr)) {
> pDev->pI2CBus = pVia->pI2CBus2;
> } else {
> // xf86DestroyI2CDevRec(pDev, TRUE);
> return;
> }</span >
Yes, that's the same offending line that I found. Removing the
xf86DestroyI2CDevRec call should fix it (haven't tried it myself) but it will
result in a memory leak (Create without a matching Destroy). That's why I
decided to patch xf86DestroyI2CDevRec to handle this better.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>