Martin Mathieson wrote:
> For the more general problem, I see 2 possible solutions:
> (1) have both signed and values in the union, and use the appropriate
> signed or unsigned parts of the union in the comparison functions
> (2) leave the union as it is with unsigned members, cast values in all
>
Could you send me a sample capture that is broken now so I can fix my
fix? :)
On Wed, Jan 03, 2007 at 09:01:26AM +0100, Kukosa, Tomas wrote:
> unfortunately it has broken calling subdissectors for packets with more
> than 1 application data records.
> As I am not sure what was exact intention of
Hi,
While looking at bug 1279 (Negative values for RTCP round trip delay
cannot be stored in guint32) I noticed that I couldn't use filter
expressions using < and negative numbers with an FT_INT32 field. The
problem seems to be that:
- fvalue_t.value.integer is a guint32
- the current less-than f
> Note that the packaging still fails though :(
>
> NMAKE : fatal error U1077: '"%ProgramFiles%\nsis\makensis.exe"' : return code
> '0x1'
> Stop.
>
Yes, already noted.
This is more related to my attempt to ease the config.nmake setting for me (and
probably others) - unfortunately this exper
Hi,
Note that the packaging still fails though :(
NMAKE : fatal error U1077: '"%ProgramFiles%\nsis\makensis.exe"' : return code
'0x1'
Stop.
BR
Anders
Från: [EMAIL PROTECTED] genom Ulf Lamping
Skickat: on 2007-01-03 15:41
Till: Developer support list for Wiresh
>
> It wouldn't be this one by any chance? Quoting myself from December 05
> <[EMAIL PROTECTED]>
>
> In openssl.h I had to change the typedef for X509_NAME and all the
> places it is used to something else because of some error I suspect (but
> couldn't prove) is a name clash. X509_NAME_SCREWS_UP
Ulf Lamping wrote:
> RABRET Laurent RD-MAPS-ISS wrote:
-snip-
>>Caution: if you test, DO NOT FORGET to compile "zlib" to ensure RT lib
>>consistency.
>>
>
> I've just disabled ZLIB (avoiding compilation of it - for now) and
> GNUTLS (strange compiler error that I don't understand) in the
> co
Hello,
unfortunately it has broken calling subdissectors for packets with more
than 1 application data records.
As I am not sure what was exact intention of this fix I do not want to
change it myself.
Help is welcome.
Regards,
Tomas
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[
