Re: [Wireshark-dev] TCP conversation analysis can be expensive, and you can't disable it

2016-04-25 Thread Guy Harris 
On Apr 25, 2016, at 4:59 PM, Guy Harris  wrote:

> When I read the capture file mentioned in bug 12367
> 
>   https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12367
> 
> it eats about 6-8GB on my machine.
> 
> A large amount of that data is in structures allocated by 
> init_tcp_conversation_data(), which is called by get_tcp_conversation_data() 
> if there isn't already one for the conversation.
> 
> get_tcp_conversation_data() is *always* called by dissect_tcp(), so you can't 
> disable that analysis.
> 
> So if you're reading a large capture file with a lot of TCP connections, make 
> sure you're on a 64-bit machine that has plenty of memory and that either has 
> or can allocate plenty of swap space to back it if necessary.

(Note: the crash on OS X isn't a "I ran out of memory so I'm calling abort()" 
crash; *maybe* it's running out of memory on Windows, given the "the 
application requested" message from Windows, but, if so, there's a separate 
problem on OS X.)

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] TCP conversation analysis can be expensive, and you can't disable it

2016-04-25 Thread Guy Harris 
When I read the capture file mentioned in bug 12367

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12367

it eats about 6-8GB on my machine.

A large amount of that data is in structures allocated by 
init_tcp_conversation_data(), which is called by get_tcp_conversation_data() if 
there isn't already one for the conversation.

get_tcp_conversation_data() is *always* called by dissect_tcp(), so you can't 
disable that analysis.

So if you're reading a large capture file with a lot of TCP connections, make 
sure you're on a 64-bit machine that has plenty of memory and that either has 
or can allocate plenty of swap space to back it if necessary.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Debian builds in wireshark

2016-04-25 Thread Born In 
Thanks Balint, Do you know if dpkg-buildpackage also builds the asn.1 
structures inside epan/dissectors/asn1// (which is usually built 
by going into the specific folder and issuing a make)?
Regards.
 

On Monday, April 25, 2016 2:06 PM, Bálint Réczey  
wrote:
 

 Hi Born,

2016-04-25 19:46 GMT+02:00 Born In :
> When I try to build an installer package for Ubuntu (Debian), I am asked
> (per the INSTALL doc in the root folder) to execute: "dpkg-buildpackage -us
> -uc -rfakeroot" before I use configure/make etc.
> However, after I checkout the source, make the required changes to the code
> and run the command, it creates a folder called debian with a bunch of files
> and directories, but no .deb files.
> Is there a place that explains this process in detail? (For ex. if I'm
> changing something inside a folder in epan/dissectors/asn1/, will the dpkg
> command internally build the changed code or do I need to compile it first
> and then run the dpkg command?
The .debs will be at ../ .

Cheers,
Balint


  ___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Debian builds in wireshark

2016-04-25 Thread Bálint Réczey 
Hi Born,

2016-04-25 19:46 GMT+02:00 Born In :
> When I try to build an installer package for Ubuntu (Debian), I am asked
> (per the INSTALL doc in the root folder) to execute: "dpkg-buildpackage -us
> -uc -rfakeroot" before I use configure/make etc.
> However, after I checkout the source, make the required changes to the code
> and run the command, it creates a folder called debian with a bunch of files
> and directories, but no .deb files.
> Is there a place that explains this process in detail? (For ex. if I'm
> changing something inside a folder in epan/dissectors/asn1/, will the dpkg
> command internally build the changed code or do I need to compile it first
> and then run the dpkg command?
The .debs will be at ../ .

Cheers,
Balint
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Debian builds in wireshark

2016-04-25 Thread Born In 
When I try to build an installer package for Ubuntu (Debian), I am asked (per 
the INSTALL doc in the root folder) to execute: "dpkg-buildpackage -us -uc 
-rfakeroot" before I use configure/make etc. 
However, after I checkout the source, make the required changes to the code and 
run the command, it creates a folder called debian with a bunch of files and 
directories, but no .deb files. 
Is there a place that explains this process in detail? (For ex. if I'm changing 
something inside a folder in epan/dissectors/asn1/, will the dpkg command 
internally build the changed code or do I need to compile it first and then run 
the dpkg command?
Regards.


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Windows buildslaves

2016-04-25 Thread Guy Harris 
On Apr 25, 2016, at 8:41 AM, Gerald Combs  wrote:

> I'll take a look.

What does "offline" mean?  I'd assumed it meant "an administrator explicitly 
shut it down because they're working on it", but does it really mean "it's not 
responding to communication from some management daemon"?
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Windows buildslaves

2016-04-25 Thread Gerald Combs 
I'll take a look.

On 4/25/16 8:19 AM, Graham Bloice wrote:
> All the Windows buildslaves seem to be offline.  Something happened at the
> hosting site?
> 
> -- 
> Graham Bloice
> 
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Windows buildslaves

2016-04-25 Thread Graham Bloice 
All the Windows buildslaves seem to be offline.  Something happened at the
hosting site?

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Commits 13dc91f5b or 9fbd4e6fc: addr_resolv.c fail to compile (async_dns_queue_head)

2016-04-25 Thread Uli Heilmeier 

I've pushed a commit to Gerrit: https://code.wireshark.org/review/15106
Hope this is ok to fix this issue.

Quoting Uli Heilmeier :


Hi list,

my build system has failed to compile current master branch since  
commits 13dc91f5b or 9fbd4e6fc.


The error is:
---
In file included from  
/usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h:9:0,

 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from addr_resolv.c:93:
addr_resolv.c: In function 'host_name_lookup_init':
addr_resolv.c:2659:14: error: 'async_dns_queue_head' undeclared  
(first use in this function)

 g_assert(async_dns_queue_head == NULL);
  ^
addr_resolv.c:2659:14: note: each undeclared identifier is reported  
only once for each function it appears in

---

c-ares is not available on my system:
---
Use c-ares library : no (name resolution will be disabled)
---

In addr_resolv.c:2659 async_dns_queue_head is called without a  
preliminary '#ifdef HAVE_C_ARES' statement


Any ideas to fix it?

Cheers
Uli




___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Commits 13dc91f5b or 9fbd4e6fc: addr_resolv.c fail to compile (async_dns_queue_head)

2016-04-25 Thread Graham Bloice 
On 25 April 2016 at 15:35, Graham Bloice 
wrote:

> On 25 April 2016 at 15:04, Uli Heilmeier  wrote:
>
>>
>> Hi list,
>>
>> my build system has failed to compile current master branch since commits
>> 13dc91f5b or 9fbd4e6fc.
>>
>> The error is:
>> ---
>> In file included from
>> /usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
>>  from /usr/include/glib-2.0/glib/gtypes.h:32,
>>  from /usr/include/glib-2.0/glib/galloca.h:32,
>>  from /usr/include/glib-2.0/glib.h:30,
>>  from addr_resolv.c:93:
>> addr_resolv.c: In function 'host_name_lookup_init':
>> addr_resolv.c:2659:14: error: 'async_dns_queue_head' undeclared (first
>> use in this function)
>>  g_assert(async_dns_queue_head == NULL);
>>   ^
>> addr_resolv.c:2659:14: note: each undeclared identifier is reported only
>> once for each function it appears in
>> ---
>>
>> c-ares is not available on my system:
>> ---
>> Use c-ares library : no (name resolution will be disabled)
>> ---
>>
>> In addr_resolv.c:2659 async_dns_queue_head is called without a
>> preliminary '#ifdef HAVE_C_ARES' statement
>>
>> Any ideas to fix it?
>>
>> Cheers
>> Uli
>>
>>
> Probably surround lines 2659 & 2660 with a #ifdef HAVE_C_ARES\#endif pair,
> and if it works then submit a change to Gerrit.
>
>
And in the next email I look a,t I see you've done exactly that.  Thanks.



-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Commits 13dc91f5b or 9fbd4e6fc: addr_resolv.c fail to compile (async_dns_queue_head)

2016-04-25 Thread Graham Bloice 
On 25 April 2016 at 15:04, Uli Heilmeier  wrote:

>
> Hi list,
>
> my build system has failed to compile current master branch since commits
> 13dc91f5b or 9fbd4e6fc.
>
> The error is:
> ---
> In file included from
> /usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
>  from /usr/include/glib-2.0/glib/gtypes.h:32,
>  from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from addr_resolv.c:93:
> addr_resolv.c: In function 'host_name_lookup_init':
> addr_resolv.c:2659:14: error: 'async_dns_queue_head' undeclared (first use
> in this function)
>  g_assert(async_dns_queue_head == NULL);
>   ^
> addr_resolv.c:2659:14: note: each undeclared identifier is reported only
> once for each function it appears in
> ---
>
> c-ares is not available on my system:
> ---
> Use c-ares library : no (name resolution will be disabled)
> ---
>
> In addr_resolv.c:2659 async_dns_queue_head is called without a preliminary
> '#ifdef HAVE_C_ARES' statement
>
> Any ideas to fix it?
>
> Cheers
> Uli
>
>
Probably surround lines 2659 & 2660 with a #ifdef HAVE_C_ARES\#endif pair,
and if it works then submit a change to Gerrit.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Commits 13dc91f5b or 9fbd4e6fc: addr_resolv.c fail to compile (async_dns_queue_head)

2016-04-25 Thread Uli Heilmeier 


Hi list,

my build system has failed to compile current master branch since  
commits 13dc91f5b or 9fbd4e6fc.


The error is:
---
In file included from  
/usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h:9:0,

 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from addr_resolv.c:93:
addr_resolv.c: In function 'host_name_lookup_init':
addr_resolv.c:2659:14: error: 'async_dns_queue_head' undeclared (first  
use in this function)

 g_assert(async_dns_queue_head == NULL);
  ^
addr_resolv.c:2659:14: note: each undeclared identifier is reported  
only once for each function it appears in

---

c-ares is not available on my system:
---
Use c-ares library : no (name resolution will be disabled)
---

In addr_resolv.c:2659 async_dns_queue_head is called without a  
preliminary '#ifdef HAVE_C_ARES' statement


Any ideas to fix it?

Cheers
Uli

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] How to download required libraries when using Cmake?

2016-04-25 Thread Graham Bloice 
On 25 April 2016 at 11:53, Graham Bloice 
wrote:

>
> On 25 April 2016 at 11:38, Anders Broman 
> wrote:
>
>> Hi,
>>
>> How are you to download the required support libraries with cmake?
>>
>> With nmake you get a warning if they are out of date and you can run the
>> setup target to have them updated. If I’m not missing something this does
>> not work with
>>
>> Cmake?
>>
>>
>>
>> Regards
>>
>> Anders
>>
>
> CMake causes the third party libs to be downloaded using the same
> PowerShell script as nmake, win-setup.ps1, however I think this is only a
> CMake generation step, not build step.  There's a comment in CMakeLists.txt:
>
> # XXX Add a dependency on ${_ws_lib_dir}/current_tag.txt?
>
> That would somehow force a run of win-setup.ps1 to be part of the build
> step.  The tricky part is sequencing it so that it would be the first
> target to be built.
>
>
>
Note that the CMake generation step is automagically done for a build if
any of the CMakeLists.txt files have changed, but there's no current
dependency to cause that to happen if the tag is changed.  As the tag is
implicit in win-setup.ps1, that could be used as a pre-build dependency.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] How to download required libraries when using Cmake?

2016-04-25 Thread Graham Bloice 
On 25 April 2016 at 11:38, Anders Broman  wrote:

> Hi,
>
> How are you to download the required support libraries with cmake?
>
> With nmake you get a warning if they are out of date and you can run the
> setup target to have them updated. If I’m not missing something this does
> not work with
>
> Cmake?
>
>
>
> Regards
>
> Anders
>

CMake causes the third party libs to be downloaded using the same
PowerShell script as nmake, win-setup.ps1, however I think this is only a
CMake generation step, not build step.  There's a comment in CMakeLists.txt:

# XXX Add a dependency on ${_ws_lib_dir}/current_tag.txt?

That would somehow force a run of win-setup.ps1 to be part of the build
step.  The tricky part is sequencing it so that it would be the first
target to be built.


-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] How to download required libraries when using Cmake?

2016-04-25 Thread Anders Broman 
Hi,
How are you to download the required support libraries with cmake?
With nmake you get a warning if they are out of date and you can run the setup 
target to have them updated. If I'm not missing something this does not work 
with
Cmake?

Regards
Anders
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe