<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 26, 2013 at 6:03 PM, Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>On Thu, Sep 26, 2013 at 05:19:20PM -0400, Matt Causey wrote:<br>
> So perhaps I'm revealing my ignorance here, but I cannot repro this<br>
> segfault under valgrind:<br>
><br>
> sudo valgrind wpa_supplicant -t -Dnl80211 -onl80211 -dddd -i wlan0 -c<br>
> /var/tmp/nerf.conf<br>
><br>
> Is there something I'm missing here?<br>
<br>
</div>valgrind can actually "hide" some crashes, but if that happened, you<br>
should see valgrind error messages.. May be it is easiest to direct them<br>
to a file ("sudo valgrind --log-file=/tmp/valgrind.log wpa_supplicant<br>
...") and check whether you'll get entries there about invalid memory<br>
accesses.<br></blockquote><div><br></div><div>I can't seem to do anything that will cause this segfault to happen w/valgrind. :-( What do you think about this:<br><br>==25997== LEAK SUMMARY:<br>==25997== definitely lost: 0 bytes in 0 blocks<br>
==25997== indirectly lost: 0 bytes in 0 blocks<br>==25997== possibly lost: 205 bytes in 18 blocks<br>==25997== still reachable: 36 bytes in 2 blocks<br>==25997== suppressed: 0 bytes in 0 blocks<br>==25997== Reachable blocks (those to which a pointer was found) are not shown.<br>
==25997== To see them, rerun with: --leak-check=full --show-reachable=yes<br>==25997== <br>==25997== For counts of detected and suppressed errors, rerun with: -v<br>==25997== Use --track-origins=yes to see where uninitialised values come from<br>
==25997== ERROR SUMMARY: 155711 errors from 129 contexts (suppressed: 27 from 6)<br><br></div><div>I've attached the full and compressed valgrind log, though it may end up being scrubbed by the server.<br><br></div><div>
Thoughts?<br><br>--<br></div><div>Matt<br><br></div><div> <br></div></div></div></div>