Ulf Lamping wrote:
> Jeff Morriss wrote:
>> Actually GCC already has a way to avoid this: "-Wno-pointer-sign".
>>
>> Apparently:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00505.html
>>
>> someone didn't like the fact that Linux had a few thousand such warnings
>> when compiled with GCC
Jeff Morriss wrote:
> Actually GCC already has a way to avoid this: "-Wno-pointer-sign".
>
> Apparently:
>
> http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00505.html
>
> someone didn't like the fact that Linux had a few thousand such warnings
> when compiled with GCC 4.
>
> We could add that and pr
Guy Harris wrote:
> The main reason for warnings you can't eliminate, I suspect, are
> crufty vendor #include headers. At least some versions of Solaris
> have, as I remember, crappy old X11 headers that don't have function
> prototypes by default, hence the hack to turn them on in configure
Luis Ontanon wrote:
> the point is what kind of warnings can be cleaned up:
>
> to fix "pointer arguments differ in signedness" for example would be
> a waste of time, as they are caused by guint8* used instaed of gchar*
> on those systems (most) that treat char as an unsigned.
Actually GCC al
I agree with Ulf. Warnings should not appear (at least most of them)
when compiling wireshark.
For the case "differ in signedness" case, you can use (guchar*). But as
it was already discussed with Guy, wireshark needs a library to handle
strings accurately. One starting point could simply be wrap
Luis Ontanon wrote:
> the point is what kind of warnings can be cleaned up:
>
Well, do you mean "cannot be cleanup up" or "I'm too lazy to clean them
up" ;-)
> to fix "pointer arguments differ in signedness" for example would be
> a waste of time, as they are caused by guint8* used instaed of
On Mar 19, 2007, at 7:04 PM, Ulf Lamping wrote:
> In my experience having a compiler warning free code is a good way to
> prevent very subtle bugs and would also be a good addition to the
> programs security - and BTW more pleasant to work with ;-)
>
> You will often hear the following excuse on
the point is what kind of warnings can be cleaned up:
to fix "pointer arguments differ in signedness" for example would be
a waste of time, as they are caused by guint8* used instaed of gchar*
on those systems (most) that treat char as an unsigned.
But in order to follow that policy you'll have
Hi List!
In my experience having a compiler warning free code is a good way to
prevent very subtle bugs and would also be a good addition to the
programs security - and BTW more pleasant to work with ;-)
You will often hear the following excuse on this topic: "but you cannot
write code which w
Graeme Lunt wrote:
> Hi,
>
> A while back, when Wireshark was being slow to startup I think, I added a
> modified splash screen to my development version (see attached image). It
> updates as each protocol is registered and then as it's handoff function is
> called.
>
> It obviously doesn't speed u
On Mar 18, 2007, at 2:37 PM, Andreas Bakurov wrote:
> I'm writing a program that should parse TCP/IP packets, currently I'm
> using libpcap for this purpose which doesn't help much (I should cast
> each packet to the header structure).
> Is there a way to reuse wireshark code ?
That depends on w
On Mon, Mar 19, 2007 at 10:45:42AM +0800, Jeff Morriss wrote:
>
> > I did however start to look into the code to see how I could implement
> > the extra field. I realise that I need to start to understand how
> > wireshark actually handles frames. Some fields are filled by the
> > dissector and s
On Mon, Mar 19, 2007 at 01:30:04AM +0100, Ulf Lamping wrote:
> After the latest GTK on Win32 lib updates (two times in recent days),
> the GTK-Wimp theme doesn't seem to work (at least on my machine) - the
> GTK2 version looks like "old style" GTK again.
>
> My first thought was a relocation of
Hi,
A while back, when Wireshark was being slow to startup I think, I added a
modified splash screen to my development version (see attached image). It
updates as each protocol is registered and then as it's handoff function is
called.
It obviously doesn't speed up initialisation, but does give s
Hi,
Webpage looks good.
You can find all you need to know for setting up a development environment
in the developer guide on the website documentation section.
The source tree contains a doc directory with README files.
README.developer is what you want to read.
Thanx,
Jaap
On Mon, 19 Mar 2007,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
binl protocol (Boot Information Negotiation Layer)
it's used by microsoft to do network installations
of windows client, I've partially reversed the proto
and I'm able to use linux or other os to do it,
I've made a little doc for the packets:
http://os
Can you send me a capture file with at least one packet containing the
TFO codec list so I can implement it.
Luis
On 3/19/07, melike pinar ata <[EMAIL PROTECTED]> wrote:
> Thank you for your help and your attention. I've installed the latest build
> (wireshark-setup-0.99.6-SVN-21064.exe), some pa
Thank you for your help and your attention. Ive installed the latest build
(wireshark-setup-0.99.6-SVN-21064.exe), some parameters still cannot to be
decoded (codecList).
Regards,
...
streamMode: sendRecv (2)
propertyParms: 3 items
Item
propertyName: 00310001 3G TFO Control (003
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hi,
Does anyone have idl2eth version for windows? I am stuck with linux
version that is usable but only on linux.
Thanks in advance,
Kristijan
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wires
20 matches
Mail list logo
