http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1967
fschorr@xxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fschorr@xxxxxxxxxxx
------- Comment #2 from fschorr@xxxxxxxxxxx 2007-11-01 03:15 GMT -------
(In reply to comment #1)
> Were your plugins compiled with the 0.99.6 headers and libraries? We don't
> currently support binary compatibility for plugins between releases.
>
I'm using 0.99.7 sources I pulled within the last week. I don't have the svn
number handy.
This same problem showed up with a copy of a 0.99.7 SVN build I pulled about
the same time. Again I don't have the specific build with me tonight but I can
look them up tomorrow and also update to the most current build tomorrow.
If I have time tomorrow I'm planning on taking these dissectors and do a build
of Wireshark with them as "internal" dissectors to see if I have the same with
them as built in dissectors too or see if the problem only shows up with them
as plugins.
On the surface at least it appears that that write access to the columns has
been turned off/disabled before my dissectors are being called.
Is there a reason why using a col_set_writable(pinfo->cinfo, TRUE); in my
dissectors don't seem to have an effect? I don't know if this is to be
expected or if this is a symptom.
I'm painfully aware that plugins are not compatible between versions of
Wireshark, sometimes I run into problems with builds from week to week! The
issues really accelerated for me starting at 0.95.5. This is the last of the
current batch of problems. Everything else is working correctly. With this
one solved I'll be able to issue a new set of plugins for 0.99.6a!
I saw one or two other bugs that seemed to be talking about similar issues -
but I think they were caused by TCP turning off write access to the columns for
frames that were part of an incomplete PDU.
Funny that in packet_tcp.c I see col_set_writable being set to FALSE and never
see it back to TRUE. I don't think this is related to my problem.. It's just
something I don't understand at this point. It would be nice if I could do
Wireshark dissector development full time rather then 1 or 2 days a month (if
I'm lucky!).
Again thanks for your time. I'm going to do some more
debugging/troubleshooting tomorrow to see if I can get sharper symptoms.
Frank
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.