forked from osmocom/wireshark
Grammar and typo fix from Mike Duigou.
svn path=/trunk/; revision=12979
This commit is contained in:
parent
88cf75d47f
commit
3d06f85155
|
@ -2398,7 +2398,7 @@ static dissector_handle_t sub_dissector_handle;
|
|||
|
||||
2.5 Per packet information
|
||||
|
||||
Information can be stored for each data packet that is process by the dissector.
|
||||
Information can be stored for each data packet that is processed by the dissector.
|
||||
The information is added with the p_add_proto_data function and retreived with the
|
||||
p_get_proto_data function. The data pointers passed into the p_add_proto_data are
|
||||
not managed by the proto_data routines. If you use malloc or any other dynamic
|
||||
|
@ -2523,7 +2523,7 @@ that includes enough information to determine the PDU length, possibly
|
|||
followed by additional data. The second one is more generic but
|
||||
requires more code and is less efficient.
|
||||
|
||||
For the first method, you register two different dissection methods, on
|
||||
For the first method, you register two different dissection methods, one
|
||||
for the TCP case, and one for the other cases. It is a good idea to
|
||||
have a dissect_PROTO_common function which will parse the generic
|
||||
content that you can find in all PDUs which is called from
|
||||
|
|
Loading…
Reference in New Issue