On Fri, Dec 17, 2010 at 12:40:44AM -0800, Guy Harris wrote:
>
> On Dec 17, 2010, at 12:37 AM, Hoang Thang wrote:
>
> > I am seeing the source code of Wireshark and confuse what
> > BASE_DEC_HEX and BASE_HEX_DEC are. Why don't we use only BASE_HEX or
> > BASE_DEC ?
>
> Because, for whatever rea
On 12/17/2010 11:20 AM, Sam Stephenson wrote:
> Where can I find the actual source code to download in order to build
> the latest version of wireshark using RHEL5?
>
> We are moving system to RHEL5 (RHEL5.5 specifically), and yes, RHEL5.5
> has included version *wireshark-1.0.8-1.el5_3.1*. But, is
On 12/17/2010 05:41 PM, Straszheim Daryl-P26342 wrote:
> Are there description comments for the enum values in the header file
> where they are defined?
>
> e.g.
>
> BASE_DEC, /* displayed as dec */
> BASE_HEX, /* displayed as hex */
> BASE_DEC_HEX, /* displayed as dec(hex) */
> BASE_HEX_DE
On Sat, Dec 18, 2010 at 10:57:29AM +0100, Andreas wrote:
[...]
> The problem I see is that Wireshark doesn't have "The API". It is not
> obvious which header files, and which declaration are public. When you
> look at the libwireshark.def it seems that definitions have been added
> or removed ju
On 12/18/2010 11:03 AM, Jeff Morriss wrote:
> On 12/18/2010 06:13 AM, Joerg Mayer wrote:
>> On Fri, Dec 17, 2010 at 09:53:09PM -0500, Bill Meier wrote:
>>> It seemed like a good idea to me. I find trying to read
>>> README.developer rather tedious, altho I do agree that a plain text file
>>> can b
Are there description comments for the enum values in the header file
where they are defined?
e.g.
BASE_DEC, /* displayed as dec */
BASE_HEX, /* displayed as hex */
BASE_DEC_HEX, /* displayed as dec(hex) */
BASE_HEX_DEC, /* displayed as hex(dec) */
-Original Message-
From: wires
Where can I find the actual source code to download in order to build
the latest version of wireshark using RHEL5?
We are moving system to RHEL5 (RHEL5.5 specifically), and yes, RHEL5.5
has included version wireshark-1.0.8-1.el5_3.1. But, is this the
equivalent to latest version 1.4.2? Since 1.3.4
On 12/18/2010 06:13 AM, Joerg Mayer wrote:
> On Fri, Dec 17, 2010 at 09:53:09PM -0500, Bill Meier wrote:
>> It seemed like a good idea to me. I find trying to read
>> README.developer rather tedious, altho I do agree that a plain text file
>> can be grep'ed and etc.
>>
>> If there's feeling that R
On Fri, Dec 17, 2010 at 09:53:09PM -0500, Bill Meier wrote:
> It seemed like a good idea to me. I find trying to read
> README.developer rather tedious, altho I do agree that a plain text file
> can be grep'ed and etc.
>
> If there's feeling that README.developer should be left as is, then I
>
Am 18.12.2010 00:48, schrieb Gregory Seidman:
> On Fri, Dec 17, 2010 at 03:40:55PM +0100, Balint Reczey wrote:
>> Hi Gregory,
>>
>> On 12/17/2010 03:21 PM, Gregory Seidman wrote:
>>> I keep running into this issue where I'm working on a dissector plugin
>>> (for internal distribution, on Windows) a
> It seemed like a good idea to me. I find trying to read
> README.developer rather tedious, altho I do agree that a plain text file
> can be grep'ed and etc.
>
> If there's feeling that README.developer should be left as is, then I
> can certainly revert the changes.
I think having one conci
11 matches
Mail list logo