Hey,
yami wrote:
> Hi,
>
> Some common false positive reasons are:
> 1. assertions are not respected, scan-build usually assume ptr is NULL
> in "DISSECTOR_ASSERT(ptr)".
I also ran into this issue and I raised a bug [1] a while back which
should reduce the amount of false positives.
[
Hello everybody,
I don't know if it is the right place to ask the question, let me know
if not.
I am currently writting a simple dissector using lua for a proprietary
protocol.
This protocol is quite basic ,i.e : frame start character+ data + frame
stop character .
But the problem is that the da
On Tue, Jun 16, 2009 at 2:37 PM, wrote:
> I thought this modification (about possibility to modify TFTP port in
> preferences) should appear in 1.2.0 release, but I have seen it's not the
> case. Do you know if it will be available in a stable release, and if yes,
> when?
Hi,
We had a feature f
Hi Stig,
I thought this modification (about possibility to modify TFTP port in
preferences) should appear in 1.2.0
release, but I have seen it's not the case. Do you know if it will be
available in a stable release, and if yes, when?
Thanks
Yvan
De : Stig Bjø
Hi All,
I have successfully able to compile Wireshark-1.0.5 on SUSE 10.2 x86_64
machine, but got following error while trying to build an rpm.
+ /usr/lib/rpm/brp-lib64-linux
s...@suse.de: if you find problems with this script, drop me a note
/tmp/wireshark-1.0.5-root/usr/lib/libwireshark.s
Hi Stig,
I thought this modification should appear in 1.2.0 release, but I have seen
it's not the case. Do you know if it will be available in a stable release, and
if yes, when?
Thanks
Yvan
De : Stig Bjørlykke
À : Developer support list for Wireshark
Env
