On Fri, 2007-07-20 at 15:59 -0700, Paul Stewart wrote:
> On Thu, 2007-06-07 at 22:39 +0530, shantanu choudhary
wrote:
> > now i am recieving a segmentation fault i am
sending client hello then
> > it stops abruptly.
> [...]
> > RX EAPOL - hexdump(len=1038)
> ^^^^
>
> I ran into this one as well while trying to debug an
EAP problem in
> wpa_supplicant as well. The error lies in common.c in
the wpa_supplicant
> sources:
>
> > static void _wpa_hexdump(int level, const char
*title, const u8 *buf,
> > size_t len, int show)
> > {
> > size_t i;
> > char out_buf[2048];
>
> Somehow I guess that an out_buf sized 2048 might not be
able to output
> a hexadecimal (and spaced) copy of a 1038 byte buffer.
It turns out that
> this problem isn't in the wpa_supplicant code proper.
It's in a patch
> that Red Hat adds to wpa_supplcant,
wpa_supplicant-0.5.7-use-syslog.patch
> that was inserted in 0.5.7-2. This patch was removed
on Jun 4 with the
> release of /wpa_supplicant-0.5.7-3.fc7. I'm just
sending this note for
> anyone who found this thread like I did after a
segfault but didn't find
> an answer to their question like I did. So if you run
into this problem
> update your wpa_supplicant rpm.
Jouni, any update on non-hacked syslog status of
wpa_supplicant?
Dan
_______________________________________________
HostAP mailing list
HostAP shmoo.com
http:/
/lists.shmoo.com/mailman/listinfo/hostap
|