On Mar 10, 2012, at 1:38 AM, Guy Harris wrote:
> If I remove those four lines, it doesn't crash - and if I put back the
> status_capture_comment_hide() call, it still doesn't crash, so it's the
> status_expert_hide() that ultimately causes the crash.
And merely removing the
gtk_widget
On Mar 10, 2012, at 10:18 AM, abhinav narain wrote:
> I believe, the data packets destined for my AP, will be decrypted by the
> hardware itself
I *don't* believe that if the hardware is running in monitor mode.
> In any case, when I get them in userland, they should be unencrypted. right?
Wr
> Oh, and one more thing:
>
> Some network adapters, when running in a mode where they supply an 802.11
> header (such as monitor mode), put some padding in between the 802.11
> header and the payload, so the 802.2 LLC header in a data frame might not
> immediately follow the 802.11 header (regardl
When the wireshark window is maximized, selecting "autoscroll" from
the "Capture
option" menu window and running the capture process, the autoscroll is
immediately lost and is no longer selected in the "Capture option" menu.
When the window is unmaximized, everything works properly.
Autoscroll is a
On Mar 9, 2012, at 4:01 AM, Anders Broman wrote:
> If I try to run /wireshark-gtk2/wireshark -k: 127 wireshark crashes in
> file_util.c in ws_load_library(gchar *library_name)
Actually, no, at least not with my tests; it appears to crash as a result of
this change between the last build that
