On Jan 8, 2010, at 2:47 PM, Alex Lindberg wrote:
> I am building a heuristic dissector that shares a common tcp port
> used by other dissectors. This same port is used in my dissector
> and thus must be checked as part of the heuristic testing. This
> port can be changed in other modules.
Alex Lindberg wrote:
> I am building a heuristic dissector that shares a common tcp port used
> by other dissectors. This same port is used in my dissector and thus
> must be checked as part of the heuristic testing. This port can be
> changed in other modules. Is there a method to read the c
I am building a heuristic dissector that shares a common tcp port used by other
dissectors. This same port is used in my dissector and thus must be checked as
part of the heuristic testing. This port can be changed in other modules. Is
there a method to read the configuration data from anothe
Julian Fielding wrote:
>
> Jeff Morriss wrote on Thu, 07 Jan 2010 11:55:02 -0500
>
> >Paul Bjork wrote:
> >> When I try to run Wireshark 1.2.5 with WinCap 4.1.1 (?, the latest
> as
> >> of today) I get just to the startup initializing screen. It says
> >>
> >> "Initializing dissectors"
I ran checkhf.pl on packet-dash.c, but it didn't pick up the duplicates,
only the following:
Unused entry: ../../packet-dash.c, hf_description_len
Unused entry: ../../packet-dash.c, hf_oqtp_reserved
Unused entry: ../../packet-dash.c, hf_reserved_bits
However, I also just ran checkAPIs.pl on it, wh
On Fri, Jan 08, 2010 at 11:39:04AM +0530, Rach, Darshan wrote:
> I am getting the following error:
> [Dissector bug, protocol DASH: proto.c:2457: failed assertion "(guint)hfindex
> < gpa_hfinfo.len"]
>
> My code looks like this:
>
> static gint hf_epg_info_bits_len = -1;
>
> {&hf_epg_info_bits_
You have some duplicates being registered.
grep "hf_" packet-dash.c | grep "static" | grep "\-1" | wc
132 6604872
grep "{&hf" packet-dash.c | wc
142 1423228
Looks like these are your culprits:
hf_description
hf_episode_title
hf_episode_title_len
hf_has_medi
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/895
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reaso
The Buildbot has detected a new failure of Ubuntu-9.10-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Ubuntu-9.10-x64/builds/15
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-9.10-x64
Build Reaso
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/1177
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Bui
Indeed! I compiled succesfully with other source files. At the time it
failed i used 31441(updated to last). Now i use the last released: 31229
that could compile succesfully. I will try again the latest with positive
hopes!
Again thank you both for your feeback!
Date: Tue, 05 Jan 2010 14:14:52
I checked all of those. I still get the same error.
Is there any other solution for this error?
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jan Gerbecks
Sent: Friday, January 08, 2010 4:31 PM
To: Developer support list for Wireshark
Subject:
This really belongs in "users", but since it is here ...
Richard Brooks wrote:
> Wireshark must have got the 'bskyb-pop3-ssl.l.google.com' result somehow. I
> can do an nslookup just after Wireshark comes back with
> 'bskyb-pop3-ssl.l.google.com' but I still get the same old vanilla flavoured
> 'p
Hi,
that usually means you forget to either:
initialize a variable
or didn't add it to the hf[] or ett[] array.
Take a closer look there,
Jan
On 08.01.2010, at 07:09, Rach, Darshan wrote:
> Hi,
>
> I am getting the following error:
> [Dissector bug, protocol DASH: proto.c:2457: failed asser
Jeff Morriss wrote on Thu, 07 Jan 2010 11:55:02 -0500
>Paul Bjork wrote:
>> When I try to run Wireshark 1.2.5 with WinCap 4.1.1 (?, the latest as
>> of today) I get just to the startup initializing screen. It says
>>
>> "Initializing dissectors"
>>
>> then it hangs and is not salvageable eve
15 matches
Mail list logo
