On Wed, 9 Nov 2011 23:58:13 +0100, Michael Tüxen wrote:
On Nov 9, 2011, at 10:30 PM, Guy Harris wrote:
On Nov 9, 2011, at 1:09 PM, Bill Meier wrote:
Any reason not to remove all the 'if (use_threads)' tests (just
leaving the threads branches of the code) ??
I think the threading code was i
On Wed, Nov 09, 2011 at 09:46:06PM +0100, Stig Bj?rlykke wrote:
> I committed a corrected fix in revision 39775.
Thanks!
> Joerg: did your grep ever finish? ;)
Probably - but it took longer than to the next important and time consuming
interruption :-)
Ciao
Joerg
--
Joerg Mayer
On Nov 9, 2011, at 10:30 PM, Guy Harris wrote:
>
> On Nov 9, 2011, at 1:09 PM, Bill Meier wrote:
>
>> Any reason not to remove all the 'if (use_threads)' tests (just leaving the
>> threads branches of the code) ??
>
> I think the threading code was introduced by Michael Tuexen and Irene
> Rün
Hi Folks,
Can someone tell me how to use wireshark protocols dissectors to
assemble/disassemble packets passed by some other program.
I want to make use of a dissector (available in wireshark ) in a python module.
Thank you!
On Nov 9, 2011, at 1:09 PM, Bill Meier wrote:
> Any reason not to remove all the 'if (use_threads)' tests (just leaving the
> threads branches of the code) ??
I think the threading code was introduced by Michael Tuexen and Irene Rüngeler
- Michael? It appears that capturing on multiple interf
On Nov 9, 2011, at 10:09 PM, Bill Meier wrote:
> On 11/9/2011 3:45 PM, s...@wireshark.org wrote:
>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=39775
>>
>> User: stig
>> Date: 2011/11/09 12:45 PM
>>
>> Log:
>> As reported by Michael Speck:
>> Removed last occurrences of US
On 11/9/2011 3:45 PM, s...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=39775
User: stig
Date: 2011/11/09 12:45 PM
Log:
As reported by Michael Speck:
Removed last occurrences of USE_THREADS.
Directory: /trunk/
ChangesPath Action
Hi.
I committed a corrected fix in revision 39775.
Joerg: did your grep ever finish? ;)
--
Stig Bjørlykke
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe:
Hi,
Well, as you said, it's more for wireshark-users, so come over there.
It's free!
Thanks,
Jaap
On Tue, 08 Nov 2011 10:08:12 +0100, Marcel Haas wrote:
Hi @ all,
first i have to say its more a question for the user mailinglist but
im
just registerd here.
So maybe someone of u can help me
Hello Michael,
On Wed, Nov 09, 2011 at 10:12:59AM +0100, Speck Michael EHWG AVL/GAE wrote:
> Thanks Guy for the fast response.
> Attached is a patch that fixes dumpcap.c
Thanks for finding and fixing this. I will check in a slightly modified
version of your fix: changing a: -> at: is not correct,
Thanks Guy for the fast response.
Attached is a patch that fixes dumpcap.c
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Guy Harris
Sent: Mittwoch, 9. November 2011 09:49
To: Developer support list for Wireshark
On Nov 9, 2011, at 12:42 AM, Speck Michael EHWG AVL/GAE wrote:
> 1.) how to tell the build system that "USE_THREADS" should be defined?
USE_THREADS should not be defined in the SVN trunk any more; threads should
always be used. Nothing in Wireshark should be checking for USE_THREADS any
more;
Hi.
I've downloaded latest sources from SVN this morning and run the sequence
make distclean
make setup
make all
that proceeded without any errors. (build system Win7-x64, for more details see
end of message)
However, Wireshark is not able to start a new capture from any interface.
13 matches
Mail list logo