Wireshark · Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 38350: /trunk/ /trunk/gtk/: capture_dlg.c capture_dlg.h

["Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>]

Here's the link to the projects: http://scan.coverity.com/rung1.html.  You'll need to sign in, but since I saw your name in the Coverity list of names for the Wireshark project, I assume you have access already?  If not, I think you can request login credentials from Coverity.


> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> bounces@xxxxxxxxxxxxx] On Behalf Of Michael Tüxen
> Sent: Monday, August 08, 2011 3:10 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 38350: /trunk/
> /trunk/gtk/: capture_dlg.c capture_dlg.h capture_if_dlg.c
> capture_if_dlg.h main_welcome.c main_welcome.h menus.c menus.h /trunk/:
> capture.c capture_ifinfo.c capture_ifinfo.h
> 
> On Aug 8, 2011, at 8:44 PM, Maynard, Chris wrote:
> 
> > FYI ... there are 8 new Coverity CID's that appear to be related to
> these recent changes, namely CID's 1250-1257.
> How can I access them?
> 
> Best regards
> Michael
> >
> >> -----Original Message-----
> >> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> >> bounces@xxxxxxxxxxxxx] On Behalf Of Michael Tuexen
> >> Sent: Friday, August 05, 2011 5:09 PM
> >> To: Developer support list for Wireshark
> >> Cc: Irene Rüngeler
> >> Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 38350: /trunk/
> >> /trunk/gtk/: capture_dlg.c capture_dlg.h capture_if_dlg.c
> >> capture_if_dlg.h main_welcome.c main_welcome.h menus.c menus.h
> /trunk/:
> >> capture.c capture_ifinfo.c capture_ifinfo.h
> >>
> >> On Aug 5, 2011, at 11:36 AM, Stig Bjørlykke wrote:
> >>
> >>> And some more comments:
> >>>
> >>> * "Capture packets in monitor mode" is enabled for devices not
> >> supporting this.
> >> If there is a way to figure out if it is supported, we should handle
> >> that correctly,
> >> I agree.
> >>> * When manually selecting all interfaces in the list, should the
> >>> checkbox "Capture on all interfaces" be automatically checked?
> >> Hmm. Not sure. Does this help? This would required counting. But it
> >> could be done.
> >>> * I get wrong link-layer for some of my remote (rpcap) devices.
> This
> >>> used to work before.
> >> Hmm. This needs to be fixed. Can you provide some hints what is
> going
> >> wrong? We haven't seen this in our testing.
> >>> * Maybe we should bring up the "Edit Interface Settings" window
> when
> >>> double-clicking the interface in the Welcome page?
> >> Maybe.
> >>> * We also need some documentation changes :)
> >> This is already on the ToDo list. But I want to get the GUI stable
> >> before Irene will work on the documentation.
> >>
> >> Best regards
> >> Michael
> >>>
> >>>
> >>> --
> >>> Stig Bjørlykke
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > CONFIDENTIALITY NOTICE: The contents of this email are confidential
> > and for the exclusive use of the intended recipient. If you receive
> this
> > email in error, please delete it from your system immediately and
> > notify us either by email, telephone or fax. You should not copy,
> > forward, or otherwise disclose the content of the email.
> >
> >
> _______________________________________________________________________
> ____
> > Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> > Archives:    http://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> >             mailto:wireshark-dev-
> request@xxxxxxxxxxxxx?subject=unsubscribe
> >
> 
> _______________________________________________________________________
> ____
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-
> request@xxxxxxxxxxxxx?subject=unsubscribe
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.