On Fri, Jun 19, 2009 at 7:53 AM, Stephen Fisher wrote:
> Hey Stig,
>
> Did you mean to commit those huge changes to packet-cip.[ch] and
> packet-enip.[ch] along with the length2 fix in packet-gblp.c? :)
Whops, no. They was for my next commit, from bug 3101.
I'll revert until review is completed
Hey Stig,
Did you mean to commit those huge changes to packet-cip.[ch] and
packet-enip.[ch] along with the length2 fix in packet-gblp.c? :)
On Fri, Jun 19, 2009 at 05:45:41AM +, s...@wireshark.org wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=28777
>
> User: stig
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/2689
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
Hi there,
With Wireshark, I'm trying to modify it to send NDIS requests to a wifi
card driver on windows OS. To do this I need to call CreateFile() and pass a
string of device name to it. However, what exactly a device name should I
pass?
I have the following device name, e.g.
\Device\NPF_{4C2
On Jun 18, 2009, at 3:11 PM, Jonathan Walker (c) wrote:
> It wasn't giving the specific error, which is why it was so hard to
> debug.
What non-specific error did it give? Did it crash? If so, could you
get a stack trace?
> It's not causing me problems anymore though. I made the array in
It wasn't giving the specific error, which is why it was so hard to debug.
It's not causing me problems anymore though. I made the array into a pointer
instead, and allocated the same amount of memory to the pointer, and for some
reason it fixed the problem.
I don't know why the array was caus
On Jun 18, 2009, at 1:43 PM, Jonathan Walker (c) wrote:
>When creating and registering a new header field array in a plug-
> in, does the size of the array have to be exactly the same as the
> number of used fields?
No. This is C, not PL/I :-), so if you pass an array (which really
mea
Hello all,
When creating and registering a new header field array in a plug-in, does
the size of the array have to be exactly the same as the number of used fields?
For example, I created a hf array as follows:
static hf_register_info hf[MAX_FIELDS];
I plan to fill up a certain variab
The Buildbot has detected a new failure of Windows-XP-Win64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-Win64/builds/724
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-win64
Build R
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/6362
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
Dear Madam/Sir,
My name is Yi huang, I am working in Ericsson Germany.
Could you kindly let me know if Wireshark have the protocol stack (BSSMAP) to
monitor A-if (between MSC and BSC)
Thanks a lot!
Br, yi
Yi Huang M.Sc.
Customer Project Manager
Multi-Vendor Integratio
On 6/15/09 1:39 PM, "Ramon F. McDougall" wrote:
> Good Afternoon,
>
> I need your help resolving this issue.
>
> Process: wireshark-bin [604]
> Path:
> /Applications/Wireshark.app/Contents/Resources/bin/wireshark-bin
> Identifier: wireshark-bin
> Version: ???
Hi,
I'm thinking of extending the slow protocol dissector to include subtype 0x0a
and would like to know if anyone else is looking at this already ?
Subtype 0x0a is used to carry Ethernet SSM for Synchronous Ethernet.
Thanks for your time,
Dave.
Hi
I just encountered a build error on windows using trunk-1.2. Maybe my
compiler options are too strict as a warning is treated as error but I
just used the default makefile...
uncommenting corresponding defines in iax2_analysis.h works.
build log:
iax2_analysis.c
D:\Projekte\wireshark\gtk/iax2
14 matches
Mail list logo
