Re: [Wireshark-dev] linking errors on Windows

2016-02-23 Thread Roland Knall
Hi Could you provide some form of linker output so that we could see, which functions you are talking about? regards Roland On Wed, Feb 24, 2016 at 6:25 AM, Edwin Groothuis < edwin.grooth...@riverbed.com> wrote: > Greetings, > > > > I’m in the process of upgrading an 1.10 environment into the 2

[Wireshark-dev] linking errors on Windows

2016-02-23 Thread Edwin Groothuis
Greetings, I'm in the process of upgrading an 1.10 environment into the 2.0 century and run in one last problem: The functions from a new file in epan/ don't get recognized by the linker for VS2013. I have added it to Makefile.common, the include file contains the WS_DLL_PUBLIC declaration. In

Re: [Wireshark-dev] Highlight fields

2016-02-23 Thread Juan Jose Martin Carrascosa
Shoot an email in this thread if you do so. I am highly interested on this feature. Thanks! Juanjo On Tuesday, February 23, 2016, Stig Bjørlykke wrote: > On Tue, Feb 23, 2016 at 9:11 PM, Jeff Morriss > wrote: > >> (A first--and useful--step would be to highlight the tree item when >> searching

Re: [Wireshark-dev] Highlight fields

2016-02-23 Thread Stig Bjørlykke
On Tue, Feb 23, 2016 at 9:11 PM, Jeff Morriss wrote: > (A first--and useful--step would be to highlight the tree item when > searching with a display filter. Or maybe that's the whole solution?) > I'm already thinking about doing this in Find Packet with a display filter, so this could be commo

Re: [Wireshark-dev] Highlight fields

2016-02-23 Thread Jeff Morriss
Hmm, this might be easier than described below. It turns out there's already some similar functionality when doing a "Find packet" when searching for a string or hex value. See: https://code.wireshark.org/review/#/c/14086/ as well as the bug that links to and the original change that added the

Re: [Wireshark-dev] [Wireshark-commits] master e282c19: autotools: Fix multiple repetitions of -L build flags

2016-02-23 Thread João Valverde
On 23-02-2016 14:14, Anders Broman wrote: *From:*wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] *On Behalf Of *Jeff Morriss *Sent:* den 23 februari 2016 15:07 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] [Wireshark-commits] master e

Re: [Wireshark-dev] Build failing on SLES 11.2

2016-02-23 Thread João Valverde
On 23-02-2016 14:31, João Valverde wrote: On 23-02-2016 14:25, João Valverde wrote: Thanks. This confirms Peter's analysis. I'll start working on a fix. But, if it the message is just a diagnostic and unknown options are ignored, was by the gcc version it really just -Qunused-arguments tha

Re: [Wireshark-dev] [Wireshark-commits] master e282c19: autotools: Fix multiple repetitions of -L build flags

2016-02-23 Thread Jeff Morriss
On Tue, Feb 23, 2016 at 9:14 AM, Anders Broman wrote: > > > > > *From:* wireshark-dev-boun...@wireshark.org [mailto: > wireshark-dev-boun...@wireshark.org] *On Behalf Of *Jeff Morriss > *Sent:* den 23 februari 2016 15:07 > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev

Re: [Wireshark-dev] Build failing on SLES 11.2

2016-02-23 Thread João Valverde
On 23-02-2016 14:25, João Valverde wrote: Thanks. This confirms Peter's analysis. I'll start working on a fix. But, if it the message is just a diagnostic and unknown options are ignored, was by the gcc version it really just -Qunused-arguments that broke the build here? On 23-02-2016 1

Re: [Wireshark-dev] Build failing on SLES 11.2

2016-02-23 Thread João Valverde
Thanks. This confirms Peter's analysis. I'll start working on a fix. On 23-02-2016 13:26, Anders Broman wrote: Hi, Here's the configure log: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by wireshark

Re: [Wireshark-dev] [Wireshark-commits] master e282c19: autotools: Fix multiple repetitions of -L build flags

2016-02-23 Thread Anders Broman
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jeff Morriss Sent: den 23 februari 2016 15:07 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] [Wireshark-commits] master e282c19: autotools: Fix multiple repetitions of -L b

Re: [Wireshark-dev] Regarding wireshark

2016-02-23 Thread Alexis La Goutte
Hi, On Sat, Feb 20, 2016 at 7:45 AM, RathnaKumar k < rathna.ku...@cangonetworks.com> wrote: > Hi , > I am making a research on wireshark .I have two questions about > wireshark.kindly,clarify that > > 1.Does wireshark support 10G interface card to capture packets. > Yes and no... Wireshark don

Re: [Wireshark-dev] [Wireshark-commits] master e282c19: autotools: Fix multiple repetitions of -L build flags

2016-02-23 Thread Jeff Morriss
On Mon, Feb 22, 2016 at 9:56 AM, Jeff Morriss wrote: > > On Mon, Feb 22, 2016 at 9:48 AM, João Valverde < > joao.valve...@tecnico.ulisboa.pt> wrote: > >> >> >> On 22-02-2016 14:28, Jeff Morriss wrote: >> >>> >>> On Sun, Feb 21, 2016 at 2:45 AM, Wireshark code review >>> >>

[Wireshark-dev] Generating DCE/RPC dissectors in Windows

2016-02-23 Thread Michael Mann
I made another attempt at trying to get DCE/RPC dissectors to generate in Windows, but still having no luck. I'll try to explain my steps/process to see if anyone has any better suggestions of things to try next. The main piece needed to generate DCE/RPC dissectors is installing the Pidl per