Hi,
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_len,
{"EPG Info Bits Length","oqtp.epg_info_bits_len",FT_UINT8, BASE_DEC,NUL
Gerald Combs wrote:
> Bill Meier wrote:
>> buildbot-no-re...@wireshark.org wrote:
>>> 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/749
>>>
>>
>>> B
It's the presence of the application that causes the warning, not the way
that Wireshark is using it. I'm sure that even if Wireshark were using it,
then it would not be using it with malicious intent.
However that said, the Secunia PSI application doesn't usually report
patched update available u
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
'pz-in-f208.1e100.net'.
Regards
Richard
-Original Message-
From: wireshark-d
Ben Greear wrote:
> I changed our LANforge protocol slightly..stealing 1 byte from the
> 'pattern' field
> to support larger payload-length.
>
> Attached is a patch against the latest wireshark svn to let wireshark
> decode this
> properly.
Please see:
http://www.wireshark.org/docs/wsdg_html/#
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 even using end task in the task
> manager.
>
> I'm running Wi
Bill Meier wrote:
> buildbot-no-re...@wireshark.org wrote:
>> 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/749
>>
>
>> BUILD FAILED: failed virus-sc
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 even using end task in the task
manager.
I'm running Windows 2000 SP4 on an instance of a v
buildbot-no-re...@wireshark.org wrote:
> 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/749
>
>
> BUILD FAILED: failed virus-scan.cmd
>
C:\buildbot\w
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/749
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason:
Richard,
I think you are not getting it.
In short, you happen to have a got a *lucky* result from the public reverse
DNS that is meaningful to you. There is no guarantee that this is going to
be the case in any other situations. In fact, for a huge amount of real
server IP addresses, you will fin
On Thu, Jan 07, 2010 at 04:05:14AM -0800, Guy Harris wrote:
>
> On Jan 7, 2010, at 3:45 AM, p...@wsh.sbrk.co.uk wrote:
>
> > Well, I am reassembling the packets in a burst transfer, but first of all
> > I have to reassemble the bytes in the USB transfer which is just a byte
> > stream.
> OK, so
On Jan 7, 2010, at 3:45 AM, p...@wsh.sbrk.co.uk wrote:
> Well, I am reassembling the packets in a burst transfer, but first of all
> I have to reassemble the bytes in the USB transfer which is just a byte
> stream.
OK, so those (reassembling the bytes in the USB transfer, and reassembling the
p
Hello Abhik
thanks for response.
after reviewing some of the code of the dissector, I guess I more interested in
the layer below the dissector.
basically I would like to find how the stream data is captured and presented to
the dissector.
it looks like tcp_dissect_pdus() performs the magic of t
On Thu, Jan 07, 2010 at 03:26:32AM -0800, Guy Harris wrote:
>
> On Jan 7, 2010, at 1:48 AM, p...@wsh.sbrk.co.uk wrote:
>
> > TCP has a tcp_dissect_pdus() function that higher protocols can use
> > to eliminate their dependency on the TCP framing. Is there anything
> > generic for other layers? I
Richard Brooks wrote:
> Hello Guy
>
> Your just not getting it.
>
> The question is given the ip address of '74.125.127.208', how does one query
> a DNS server (in this case DNS ip 8.8.8.8 = public Google DNS) to get the
> reply 'bskyb-pop3-ssl.l.google.co' (which is the reply Wireshark gets), a
On Jan 7, 2010, at 1:48 AM, p...@wsh.sbrk.co.uk wrote:
> TCP has a tcp_dissect_pdus() function that higher protocols can use
> to eliminate their dependency on the TCP framing. Is there anything
> generic for other layers? I'm writing a USB dissector which is really
> a serial protocol being tra
On Thu, Jan 07, 2010 at 02:09:43AM -0800, Guy Harris wrote:
> On Jan 7, 2010, at 1:48 AM, p...@wsh.sbrk.co.uk wrote:
> > TCP has a tcp_dissect_pdus() function that higher protocols can use
> > to eliminate their dependency on the TCP framing. Is there anything
> > generic for other layers?
> I
On Jan 7, 2010, at 1:48 AM, p...@wsh.sbrk.co.uk wrote:
> TCP has a tcp_dissect_pdus() function that higher protocols can use
> to eliminate their dependency on the TCP framing. Is there anything
> generic for other layers?
I.e., for other byte-stream-oriented layers? tcp_dissect_pdus() resides
TCP has a tcp_dissect_pdus() function that higher protocols can use
to eliminate their dependency on the TCP framing. Is there anything
generic for other layers? I'm writing a USB dissector which is really
a serial protocol being transported over USB. Most of the time
there is only one packet with
Hi,
At the time of 1.2.5 GTK 2.16.2 was the latest version...
Besides gdk_window_begin_implicit_paint() is not used by Wireshark
So most probably this is a non issue.
Regards
Anders
-Ursprungligt meddelande-
Från: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.
21 matches
Mail list logo
