From Richard van der Hoff:
authorjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 5 Mar 2007 20:25:54 +0000 (20:25 +0000)
committerjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 5 Mar 2007 20:25:54 +0000 (20:25 +0000)
commita2ed9d4aa5fc6811dc5a44c3873a91f8fb4ee389
treef0c91f742602fb258f752be0619ff4b94141ba66
parentca1d0a3012ad9e7c35c13b936f1052c4237acf23
From Richard van der Hoff:
I've had a good look at the code in packet-tcp.c, and whilst it's
somewhat impenetrable, I've come to the conclusion that it just doesn't
support multiple pdus as described.

That's not entirely unreasonable in itself; my objection is solely to
the fact that README.developer is completely misleading. In fact, even
the example dissect_cstr won't work on the tcp dissector, because if you
set desegment_len=1 the tcp dissector believes that you know what you
are doing and doesn't let you change your mind later.

Furthermore, 2.7.2 says that you can set desegment_len=-1; that doesn't
work either, because the tcp dissector expects
DESEGMENT_ONE_MORE_SEGMENT, which is 0x0fffffff, which is nowhere near -1.

In short, I think the relevant section of README.developer needs a
rewrite. I attach a patch - comments welcome.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@20974 f5534014-38df-0310-8fa8-9805f1628bb7
doc/README.developer