On Aug 10, 2011, at 11:26 PM, Bill Meier wrote:
> capture_dlg.c: In function ‘insert_new_rows’:
>
> capture_dlg.c:665:18: warning: variable ‘cap_settings’ set but not used
> [-Wunused-but-set-variable]
> capture_dlg.c:664:8: warning: variable ‘linktype_select’ set but not used
> [-Wunused-but-s
The Buildbot has detected a new failure on builder Windows-7-x64 while building
Wireshark (development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2663
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-
On Wed, Aug 10, 2011 at 11:16:55PM +0200, Jakub Zawadzki wrote:
> On Wed, Aug 10, 2011 at 10:49:47PM +0200, Michael Tüxen wrote:
> > I was aware of this in the context of the -i arguments, but not that it
> > could be
> > specified in the GUI. We need to find a way to do this. Maybe an button
> >
> Maybe an button which
> will add a named pipe to the list of interfaces.
If this added the pipe to a preference file that would be even better, as it
would persist between Wireshark sessions. It might help pipes feel more
loved, and not like a hack added on.
Regards,
-Colin
-Original Me
capture_dlg.c: In function ‘insert_new_rows’:
capture_dlg.c:665:18: warning: variable ‘cap_settings’ set but not used
[-Wunused-but-set-variable]
capture_dlg.c:664:8: warning: variable ‘linktype_select’ set but not
used [-Wunused-but-set-variable]
capture_dlg.c: In function ‘create_and_fill_
The Buildbot has detected a new failure on builder Visual-Studio-Code-Analysis
while building Wireshark (development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Visual-Studio-Code-Analysis/builds/1603
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildsla
Buildbot.wireshark.org has been upgraded to Buildbot 0.8.4p2 (the latest
release). The new version includes an updated web interface and the
ability to do more efficient Subversion checkouts. If you run into any
issues please don't hesitate to send me an email or open a bug.
___
On Wed, Aug 10, 2011 at 10:49:47PM +0200, Michael Tüxen wrote:
> I was aware of this in the context of the -i arguments, but not that it could
> be
> specified in the GUI. We need to find a way to do this. Maybe an button which
> will add a named pipe to the list of interfaces.
Can we have it in
The Buildbot has detected a new failure on builder Windows-7-x64 while building
Wireshark (development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2661
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-
Dear all,
earlier today, I revoked my pending DVB-CI patch for spdu reassembly as
I found a problem :-(
I now think I know what happens, I'd appreciate your opinion how to deal
with it properly:
a tdpu looks like
header | body | trailer
Depending on header info, the body may contain a fragment
On Aug 10, 2011, at 1:49 PM, Michael Tüxen wrote:
> I was aware of this in the context of the -i arguments, but not that it could
> be
> specified in the GUI. We need to find a way to do this. Maybe an button which
> will add a named pipe to the list of interfaces.
If you cannot type the name o
On Aug 10, 2011, at 10:44 PM, Guy Harris wrote:
>
> On Aug 10, 2011, at 1:33 PM, Michael Tüxen wrote:
>
>> Use the command line options... There is currently no way to specify a named
>> pipe in the GUI. I think there was no way to do this in Wireshark 1.6, or
>> am I missing something?
>
> The
On Aug 10, 2011, at 10:37 PM, Colin O'Flynn wrote:
> Hello,
>
> It was possible to type over the interface name in the previous dialog with
> the named pipe. This is described at
> http://wiki.wireshark.org/CaptureSetup/Pipes ("3. The named pipe is not
> listed in the drop-down interface selectio
On Aug 10, 2011, at 1:33 PM, Michael Tüxen wrote:
> Use the command line options... There is currently no way to specify a named
> pipe in the GUI. I think there was no way to do this in Wireshark 1.6, or
> am I missing something?
The general convention in Wireshark-the-project (i.e., Wireshark,
Hello,
It was possible to type over the interface name in the previous dialog with
the named pipe. This is described at
http://wiki.wireshark.org/CaptureSetup/Pipes ("3. The named pipe is not
listed in the drop-down interface selection, and must be typed into the
interface box. On Windows, it must
On Aug 10, 2011, at 10:06 PM, Colin O'Flynn wrote:
> Hello,
>
> With the changes committed in rev 38350 which has a new capture options
> dialog, how does one use a named pipe? I couldn’t see a way to get this
> working.
Use the command line options... There is currently no way to specify a na
Hello,
With the changes committed in rev 38350 which has a new capture options
dialog, how does one use a named pipe? I couldn't see a way to get this
working.
Thanks,
-Colin
___
Sent via:Wireshark-dev mailin
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/3710
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
On 10/08/2011 18:00, Guy Harris wrote:
> On Aug 10, 2011, at 9:18 AM, news.gmane.com wrote:
>
>> I am a bit surprised about a problem with compiling Wireshark 1.6.0 with
>> Visual Studio 2005 for Win32. Some dissectors have assignments from 64 to 32
>> bit, what will issue a warning C4244 by the
On Aug 9, 2011, at 11:25 PM, pang liang wrote:
> If I want to add a new dialog file in gtk document, how to modify the
> configure file?
What do you mean by "dialog file" and "gtk *document*"? If you're adding a new
dialog to the Wireshark UI, you have to add C code in the "gtk" directory. Y
On Aug 10, 2011, at 9:18 AM, news.gmane.com wrote:
> I am a bit surprised about a problem with compiling Wireshark 1.6.0 with
> Visual Studio 2005 for Win32. Some dissectors have assignments from 64 to 32
> bit, what will issue a warning C4244 by the compiler. Since the -WX
> parameter is pass
On 10/08/2011 17:18, news.gmane.com wrote:
> Hello,
>
> I am a bit surprised about a problem with compiling Wireshark 1.6.0 with
> Visual Studio 2005 for Win32. Some dissectors have assignments from 64 to 32
> bit, what will issue a warning C4244 by the compiler. Since the -WX
> parameter is pas
Hello,
I am a bit surprised about a problem with compiling Wireshark 1.6.0 with
Visual Studio 2005 for Win32. Some dissectors have assignments from 64 to 32
bit, what will issue a warning C4244 by the compiler. Since the -WX
parameter is passed to the compiler, the compilation fails. The warnin
ANISH M wrote:
>
>I want to generate some ASN.1 PER traffic, is there any tools available for
>that? Please let me know.
It's not clear exactly what you're asking. ASN.1 is a notation to express a
protocol and PER is a means of encoding it. What's missing from your question
is some particular
Hi All,
I want to generate some ASN.1 PER traffic, is there any tools available for
that? Please let me know.
Thanks
Best Regards,
Anish
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists
If I want to add a new dialog file in gtk document, how to modify the
configure file?
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mai
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/3707
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
27 matches
Mail list logo
