Re: [Wireshark-dev] size_t under Windows ...

Not necessarily, in certain variations building WinXP and Win7 can lead to size_t being 4 byte, but the pointer PVOID either 8 byte or 4 byte depending on the target compile environment. I would stick with a definition of size_t, because others will have to handle the right size, not us. cheers

Re: [Wireshark-dev] size_t under Windows ...

On 24 November 2017 at 12:23, Roland Knall wrote: > Not necessarily, in certain variations building WinXP and Win7 can lead to > size_t being 4 byte, but the pointer PVOID either 8 byte or 4 byte > depending on the target compile environment. > > This is incorrect, as noted

Re: [Wireshark-dev] OSX build fails

On 22-11-2017 13:35, João Valverde wrote: On 22-11-2017 12:22, Anders Broman wrote: It also feels like we are raising the bar on building and distribute Wireshark on older systems. Which may be OK but perhaps better done in 3.0, I think we also Need to set the level of required packages

Re: [Wireshark-dev] size_t under Windows ...

Couldn't it be replaced by guint32 then, and the guard removed? On Fri, Nov 24, 2017 at 10:45 AM, Helge Kruse wrote: > DWORD is a 32 bit unsigned integer. > size_t is platform dependent, 32 bits in 32 bit Windows and 64 bits in > 64 bit Windows. I assume this is similar in

Re: [Wireshark-dev] size_t under Windows ...

DWORD is a 32 bit unsigned integer. size_t is platform dependent, 32 bits in 32 bit Windows and 64 bits in 64 bit Windows. I assume this is similar in other OS like Linux. Therfore you can't replace DWORD by size_t without checking the impact. Further there is an additional member cap_pipe_buf in

Re: [Wireshark-dev] size_t under Windows ...

On Fri, Nov 24, 2017 at 11:52 AM, Guy Harris wrote: > On Nov 23, 2017, at 2:12 PM, Richard Sharpe > wrote: > >> I am running into problems with this in my latest build: >> >> #if defined(_WIN32) >>char * cap_pipe_buf;

Re: [Wireshark-dev] Problems building register.c with older glib g_async_queue_timeout_pop()

João Valverde wrote:   if (!g_file_get_contents(list, , NULL, NULL))   return; -    for (arg = strtok(contents, " \n"); arg != NULL; arg = strtok(NULL, " \n")) { +    for (arg = strtok(contents, " \r\n"); arg != NULL; arg = strtok(NULL, " \r\n")) {   scan_file(arg, protos,

Re: [Wireshark-dev] Processing packet before exporting it.

W dniu 2017-11-22 18:02, Pascal Quantin napisał(a): There was indeed an experimental packet editor, but it was very limited (basically as far as I can remember it could edit values like what you could do with an hex editor, but was not a generic encoder for any given protocol). It was a

Re: [Wireshark-dev] Problems building register.c with older glib g_async_queue_timeout_pop()

On 24-11-2017 20:38, Gisle Vanem wrote: João Valverde wrote:   if (!g_file_get_contents(list, , NULL, NULL))   return; -    for (arg = strtok(contents, " \n"); arg != NULL; arg = strtok(NULL, " \n")) { +    for (arg = strtok(contents, " \r\n"); arg != NULL; arg = strtok(NULL, "

Re: [Wireshark-dev] size_t under Windows ...

On Nov 23, 2017, at 2:12 PM, Richard Sharpe wrote: > I am running into problems with this in my latest build: > > #if defined(_WIN32) >char * cap_pipe_buf; /**< Pointer > to the buffer we read into */ >DWORD

Re: [Wireshark-dev] size_t under Windows ...

On Nov 24, 2017, at 12:03 PM, Richard Sharpe wrote: > > 110>C:\buildbot\builders\windows-x86-64-petri-dish\windows-x86-64-petri-dish\build\dumpcap.c(2425): > warning C4267: '=': conversion from 'size_t' to 'DWORD', possible loss > of data > > which seems to be

[Wireshark-dev] RPM Build fails on SUSE 11.4

Hi, I get the following error doing make rpm-build: RPM build errors: File listed twice: /usr/local/bin/dumpcap Installed (but unpackaged) file(s) found: /usr/local/share/doc/wireshark/guides/wsug_html_chunked/AppFiles.html

[Wireshark-dev] (无主题)

发自网易邮箱大师 ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev

[Wireshark-dev] use -M parameter lead to auto shut down

hello first so sorry for send an empty to all of you and i type tshark -M 1000 in commandline but after few seconds it shut down him self so any one can tell me what happened？ thank you 发自网易邮箱大师 ___ Sent via:

Re: [Wireshark-dev] use -M parameter lead to auto shut down

On Nov 24, 2017, at 9:12 AM, 杜 伟强 wrote: > i type tshark -M 1000 in commandline > but after few seconds it shut down him self > so any one can tell me what happened？ It probably crashed because of a bug. Please file a bug report at