Peter Johansson wrote: > I compiled Wireshark with HAVE_AIRPDCAP by mistake (since I do not > have AirPcap). This leads to a runtime problem however. When > choosing "options" from the "Capture interfaces" dialog, I receive a > modal dialogue with an OK button with a textual description that is > only garbage (uninitialized memory). > > The provided patch adds a new error - AIRPCAP_NOT_LOADED (2) code to > the airpcap loader that also adds the text "AirPcap was expected to > be loaded but is not" to the modal dialogue instead of the > uninitialized string.
Hmm, I think you found the problem of bug 1377: http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1377 Having a quick look, though, I am a bit confused because it doesn't appear anybody ever allocates any space for 'err_str' before calling though maybe I'm missing it. Anyway I don't really have time to dig further for the moment. Another thing that needs a look is it appears that it's normal that AirPcap is compiled in (I didn't change my setup and my Windoze builds say "with Airpcap") though in that case I'm not sure it should be complaining at all if it doesn't find an AirPcap device or whatever. _______________________________________________ Wireshark-dev mailing list [email protected] http://www.wireshark.org/mailman/listinfo/wireshark-dev
