Re: [Wireshark-dev] [Wireshark-commits] rev 24995: /trunk/gtk/ /trunk/gtk/: about_dlg.c gui_utils.c gui_utils.h main_proto_draw.c webbrowser.c

2008-04-14 Thread Graeme Lunt
Stig, On 14/04/2008, Stig Bjørlykke <[EMAIL PROTECTED]> wrote: > On 13. april. 2008, at 19.48, [EMAIL PROTECTED] wrote: > > XXX: I have been unable to test this on MacOS or Linux. Stig? :-) > > Splitting the MIB/PIB paths does not work, fixed in revision 25004. Thanks. > On OSX: Everything op

Re: [Wireshark-dev] Switching to getopt_long() - or to g_option?

2008-04-14 Thread Ulf Lamping
Guy Harris schrieb: > [EMAIL PROTECTED] wrote: > > >> --- Comment #1 from Andrew Feren <[EMAIL PROTECTED]> 2008-04-14 11:35:31 >> GMT --- >> The choice of -x for the commandline argument was arbitrary. I didn't see >> any >> particular reasoning for the other switch choices so I started at z

[Wireshark-dev] mixed strdup() with g_free()

2008-04-14 Thread Ulf Lamping
Hi! In SVN25037 I've replaced some strdup() with calls to g_strdup(). If you want to free the allocated memory later with g_free(), this doesn't work (at least) on MSVC2005 builds! However, this is unclean and potentially dangerous on other systems as well - AFAIK GLib makes no guarantees what

Re: [Wireshark-dev] Problems building on Windows XP

2008-04-14 Thread Ulf Lamping
L. Mark Pilant schrieb: > I started with a fresh copy of Wireshark (to revision 25024) to a new > directory and a clean wireshark-win32-libs directory (I renamed the > "old" one to force fresh fetching of the files). Then I did: > >nmake -f Makefile.nmake distclean >nmake -f Makefile.nmake

Re: [Wireshark-dev] Hi, I need help

2008-04-14 Thread Visser, Martin
Khurram, What exactly is "real-time"? I actually think displaying I/O graphs within 2 or 3 seconds of receiving is very much real-time (particular compared to say SNMP type tools). If you mean within a micro-second then the overhead of display 100 000 packets per second is not going to be very

Re: [Wireshark-dev] Adding an IP Peer Protool

2008-04-14 Thread Jaap Keuter
Hi, I would suggest you familiarize yourself with README.developer in the doc directory of the sourcetree to get an idea what is where and how to go about this. The Wiki may also prove a valuable source of info, as is the developer guide. Thanx, Jaap Gil Berglass wrote: > I want to add an exp

[Wireshark-dev] Adding an IP Peer Protool

2008-04-14 Thread Gil Berglass
I want to add an experimental protocol carried in ethernet frames--an "IP Peer". Can someone tell me what files I need to change in the Wireshark 1.0 source to make this happen? Thanks, Gil Berglass ___ Wireshark-dev mailing list Wireshark-dev

[Wireshark-dev] Hi, I need help

2008-04-14 Thread khurram Iqbal
Hello, I have one question in my mind related wirshark. Weknow that the Wireshark provides the real time packet analysis but whenyou see the IO Graphs, you don't get real time thing. It means that thepacket is coming but on the IO graphs, you can see parametersapproximately 2 or 3 seconds lat

Re: [Wireshark-dev] Switching to getopt_long() - or to g_option?

2008-04-14 Thread Andrew Feren
I vote for moving to getopt_long or the moral equivalent (I'm not familiar with GOptions). The options for capinfos at least seem quite random. It would be very nice to be able to create some switches with meaningful names. Something that I could remember the meanings of when I read my script

[Wireshark-dev] Problems building on Windows XP

2008-04-14 Thread L. Mark Pilant
I started with a fresh copy of Wireshark (to revision 25024) to a new directory and a clean wireshark-win32-libs directory (I renamed the "old" one to force fresh fetching of the files). Then I did: nmake -f Makefile.nmake distclean nmake -f Makefile.nmake setup nmake -f Makefile.nmake

[Wireshark-dev] Switching to getopt_long() - or to g_option?

2008-04-14 Thread Guy Harris
[EMAIL PROTECTED] wrote: > --- Comment #1 from Andrew Feren <[EMAIL PROTECTED]> 2008-04-14 11:35:31 GMT > --- > The choice of -x for the commandline argument was arbitrary. I didn't see any > particular reasoning for the other switch choices so I started at z and worked > backwards until I foun

[Wireshark-dev] buildbot failure in OSX-10.4-PPC

2008-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.4-PPC. Full details are available at: http://buildbot.wireshark.org/trunk/OSX-10.4-PPC/builds/2411 Buildbot URL: http://buildbot.wireshark.org/trunk/ Build Reason: Build Source Stamp: HEAD Blamelist: ulfl BUILD FAILED: failed compile sincerely

[Wireshark-dev] Building libsmi from SVN as a .dll

2008-04-14 Thread Anders Broman
Hi, I have experemented with building libsmi.dll from libsmi SVN http://www.ibr.cs.tu-bs.de/svn/libsmi with the included makefile-dll and smi.def file It builds under MSVC6 I have not tested it but if some one likes to play with it - here it is... If you find any errors please let me know. Regards

[Wireshark-dev] buildbot failure in OSX-10.4-PPC

2008-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.4-PPC. Full details are available at: http://buildbot.wireshark.org/trunk/OSX-10.4-PPC/builds/2403 Buildbot URL: http://buildbot.wireshark.org/trunk/ Build Reason: Build Source Stamp: HEAD Blamelist: gal,ulfl BUILD FAILED: failed compile since

Re: [Wireshark-dev] [Wireshark-commits] rev 24995: /trunk/gtk/ /trunk/gtk/: about_dlg.c gui_utils.c gui_utils.h main_proto_draw.c webbrowser.c

2008-04-14 Thread Guy Harris
[EMAIL PROTECTED] wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=24995 > > User: gal > Date: 2008/04/13 05:48 PM > > Log: > Allow the folders in the About Wireshark/Folders list to be double clicked > on to open the appropriate folder in explorer. > > The MIB/PIB

Re: [Wireshark-dev] [Wireshark-commits] rev 24995: /trunk/gtk/ /trunk/gtk/: about_dlg.c gui_utils.c gui_utils.h main_proto_draw.c webbrowser.c

2008-04-14 Thread Stig Bjørlykke
On 13. april. 2008, at 19.48, [EMAIL PROTECTED] wrote: > XXX: I have been unable to test this on MacOS or Linux. Stig? :-) Splitting the MIB/PIB paths does not work, fixed in revision 25004. On OSX: Everything opens perfectly in Finder. On Ubuntu Linux: Everything opens in Firefox. I don't know

Re: [Wireshark-dev] se_tree_foreach() not compiling under XP

2008-04-14 Thread Ulf Lamping
[EMAIL PROTECTED] schrieb: > > Hello > > I can’t compile my code with the function se_tree_foreach (from > emem.h), I got following error (if I comment out the function it runs > sucessfully): > > LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of > other libs; use/NODEFAULTLIB:li

[Wireshark-dev] buildbot failure in OSX-10.4-PPC

2008-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.4-PPC. Full details are available at: http://buildbot.wireshark.org/trunk/OSX-10.4-PPC/builds/2408 Buildbot URL: http://buildbot.wireshark.org/trunk/ Build Reason: Build Source Stamp: HEAD Blamelist: ulfl BUILD FAILED: failed compile sincerely

Re: [Wireshark-dev] se_tree_foreach() not compiling under XP

2008-04-14 Thread Stephen Fisher
On Sun, Apr 13, 2008 at 06:39:32PM +0200, [EMAIL PROTECTED] wrote: > I can't compile my code with the function se_tree_foreach (from > emem.h), I got following error (if I comment out the function it runs > sucessfully): > LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of > o

Re: [Wireshark-dev] se_tree_foreach() not compiling under XP

2008-04-14 Thread Luis EG Ontanon
Hello, se_tree_foreach is not listed in libwireshark.def, *nix.so don't use it while windows dlls do. On Sun, Apr 13, 2008 at 6:39 PM, <[EMAIL PROTECTED]> wrote: > > > > > Hello > > I can't compile my code with the function se_tree_foreach (from emem.h), I > got following error (if I comment ou

[Wireshark-dev] buildbot failure in Ubuntu-7.01-x86-64

2008-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-7.01-x86-64. Full details are available at: http://buildbot.wireshark.org/trunk/Ubuntu-7.01-x86-64/builds/3103 Buildbot URL: http://buildbot.wireshark.org/trunk/ Build Reason: Build Source Stamp: HEAD Blamelist: jake,stig,tuexen,ulfl BUILD FAIL