[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

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/2346 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

[Wireshark-dev] Dissector bug?

I'm getting the following error message while running my dissector: [Dissector bug, protocol MP UDP: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address] [Expert Info (Error/Malformed): STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address] [Message: S

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1201 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

Hi On Mon, Feb 28, 2011 at 9:55 AM, Roland Knall wrote: > On Mon, Feb 28, 2011 at 9:51 AM, Guy Harris wrote: >> So my question is, can I influence the decision made by wireshark in >> any way, which plugin get's called? > > Try disabling the dissector for the protocol whose dissector you don't

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/1198 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason:

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/2130 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reas

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

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/2470 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

The Buildbot has detected a new failure of OSX-10.6-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/2023 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Bui

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

On Mon, Feb 28, 2011 at 9:51 AM, Guy Harris wrote: > > On Feb 28, 2011, at 12:32 AM, Roland Knall wrote: >> On Windows, the SercosIII plugin takes precedence over my plugin. Both >> register the same Ethertypes, therefore this should not be unusual, > > If you mean "it's not unusual that random st

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

On Feb 28, 2011, at 12:32 AM, Roland Knall wrote: > My main development plattform is Linux. On it, my plugin get's loaded, > everything get's dissected correctly, and works as intended. My plugin > is called openSAFETY. > > On Windows, the SercosIII plugin takes precedence over my plugin. Both >

[Wireshark-dev] Different wireshark behaviour on Linux as on Windows

Hello I am developing a plugin, which will dissect protocols, where other dissectors are already registered. Two instances are the Ethernet Powerlink dissector as well as the Sercos III dissector. My protocol is part of their communication messages, but can not be identified as easily, as e.g. a