Re: [Wireshark-dev] OPCUA Update

2009-04-03 Thread philippe alarcon
;tcp.port", global_mikey_tcp_port, mikey_handle); mikey_tcp_port = global_mikey_tcp_port; } I hope this will help you. Regards Philippe From: gerhard.gappme...@ascolab.com To: wireshark-dev@wireshark.org Date: Wed, 1 Apr 2009 18:32:45 +0200 Subject: [Wireshark-dev] OPCUA Update Hi all, the most OPC

Re: [Wireshark-dev] OPCUA Update

2009-04-02 Thread Gerhard Gappmeier
I added it to bugzilla. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3385 On Wednesday 01 April 2009 23:44:06 Stephen Fisher wrote: > Would you mind opening a bug at https://bugs.wireshark.org and marking > it as an enhancement and attaching the patch file and contents of your > e-mail so t

Re: [Wireshark-dev] OPCUA Update

2009-04-01 Thread Stephen Fisher
Would you mind opening a bug at https://bugs.wireshark.org and marking it as an enhancement and attaching the patch file and contents of your e-mail so the patch doesn't get missed? Steve ___ Sent via:Wireshark-dev mai

Re: [Wireshark-dev] OpcUa update

2007-05-15 Thread Ulf Lamping
Gerhard Gappmeier wrote: > Hi, > > I removed the unused variables and renamed the files with "ua_" prefix > to "opcua_" to be consistent. > I hope renaming works with the patch file... > Hi! I've tried to apply your patch, but as I've expected the renaming and the code change didn't worked wel

[Wireshark-dev] OpcUa update

2007-05-15 Thread Gerhard Gappmeier
Hi, I removed the unused variables and renamed the files with "ua_" prefix to "opcua_" to be consistent. I hope renaming works with the patch file... regards, Gerhard. Index: Makefile.common === --- Makefile.common (revision 217

Re: [Wireshark-dev] OpcUa update

2007-05-14 Thread Gerhard Gappmeier
Hi Ulf > Gerhard Gappmeier wrote: > >> Ragarding VS2005. I know that problem from other projects. >> >> * time_t is 64 bit now: Use the define _USE_32BIT_TIME_T to make >> it backward compatible >> > Well, the crash is a problem in the "compilers code" and not in our code > - I d

Re: [Wireshark-dev] OpcUa update

2007-05-14 Thread Ulf Lamping
Gerhard Gappmeier wrote: > > Ragarding VS2005. I know that problem from other projects. > > * time_t is 64 bit now: Use the define _USE_32BIT_TIME_T to make > it backward compatible > Well, the crash is a problem in the "compilers code" and not in our code - I don't know if setting this

Re: [Wireshark-dev] OpcUa update

2007-05-09 Thread Gerhard Gappmeier
Hi Ulf, sounds good. Ragarding VS2005. I know that problem from other projects. * time_t is 64 bit now: Use the define _USE_32BIT_TIME_T to make it backward compatible * wchar_t is a built-in type now. This may also cause problems, because it was a "unsigned short" before. Bu

Re: [Wireshark-dev] OpcUa update

2007-05-09 Thread Ulf Lamping
Gerhard Gappmeier wrote: > Nevertheless I attached an update where I fixed the missing { 0, NULL > }entries > in the value_string arrays. Good, that had to be fixed anyway. > I also attached the result of tshark so you can compare it with yours. > Is the access violation catched in any way and pro

Re: [Wireshark-dev] OpcUa update

2007-05-07 Thread Ulf Lamping
Gerhard Gappmeier wrote: > it loads the file imediately on my computer without any delay. > I tried the fuzzy file also with tshark. > I called "tshark -r sample.cap", is this right? > Because it didn't crash for me. I tried it several times. > > Any ideas why it behaves different for you? > I'm cu

Re: [Wireshark-dev] OpcUa update

2007-05-07 Thread Gerald Combs
Gerhard Gappmeier wrote: > Hi, > >> A fuzzed Sample.cap file (attached) crashed TShark and took a *very* >> long time (2 mins) to load in WS. >> > it loads the file imediately on my computer without any delay. > I tried the fuzzy file also with tshark. > I called "tshark -r sample.cap", is this ri

Re: [Wireshark-dev] OpcUa update

2007-05-07 Thread Gerhard Gappmeier
Hi, > A fuzzed Sample.cap file (attached) crashed TShark and took a *very* > long time (2 mins) to load in WS. > it loads the file imediately on my computer without any delay. I tried the fuzzy file also with tshark. I called "tshark -r sample.cap", is this right? Because it didn't crash for me. I