Lines Matching refs:tvbuff

229 NOTE: See the file /epan/tvbuff.h for more details.
407 from the specified tvbuff, starting at the specified offset.
420 data from the specified tvbuff, starting at the specified offset, and containing
430 containing data from the specified tvbuff, starting at the specified
431 offset, and containing all characters from the tvbuff up to and
432 including a terminating null character in the tvbuff. Reads data in the
443 specified tvbuff, starting at the specified offset, and containing all
444 bytes from the tvbuff up to and including a terminating null character
445 in the tvbuff. "*lengthp" will be set to the length of the string,
480 Formats a bunch of data from a tvbuff as bytes, returning a pointer
496 Given a tvbuff, an offset into the tvbuff, and a length that starts
498 tvbuff"), fetch the hex-decoded byte values of the tvbuff into the
500 words, convert from a hex-ascii string in tvbuff, into the supplied
505 Given a tvbuff, an offset into the tvbuff, and a length that starts
507 tvbuff"), fetch BCD encoded digits from a tvbuff starting from either
511 Note: a tvbuff content of 0xf is considered a 'filler' and will end the conversion.
517 from the specified tvbuff, starting at the specified offset.
1422 'tvb' argument is the tvbuff from which the item's value is being
1424 tvbuff of the item being added, and the 'length' argument is the length,
1447 from the tvbuff by proto_tree_add_item(), based on the type of the field
1664 but also either wish for the retrieved value from the tvbuff to be handed
1666 from the tvbuff in a string-encoded format.
1670 from the tvbuff, based on the type of the XXX name and the encoding of
1678 be decoded from the tvbuff, then an expert info error is reported. For string
2218 is expected to create a new tvbuff of type TVBUFF_SUBSET which
2223 parent tvbuff, and runs to the end of the parent tvbuff, the routine
2229 tvb is the tvbuff that the dissector has been working on. It
2230 can be a tvbuff of any type.
2234 offset is the byte offset of 'tvb' at which the new tvbuff
2238 parent tvbuff, with a specified number of bytes in the payload, the
2244 tvb is the tvbuff that the dissector has been working on. It
2245 can be a tvbuff of any type.
2249 offset is the byte offset of 'tvb' at which the new tvbuff
2263 tvb is the tvbuff that the dissector has been working on. It
2264 can be a tvbuff of any type.
2268 offset is the byte offset of 'tvb' at which the new tvbuff
3189 the tvbuff pointer, packet_info pointer, and proto_tree pointer
3198 a routine that takes as arguments a packet_info pointer, a tvbuff
3199 pointer and an offset value representing the offset into the tvbuff
3208 a new_dissector_t routine to dissect the pdu that's passed a tvbuff
3210 user data, with the tvbuff containing a possibly-reassembled PDU. (The
3211 "reported_length" of the tvbuff will be the length of the PDU);
3223 Your dissect_PROTO will initially be passed a tvbuff containing the payload of
3225 contain more than one complete PDU. If the end of the provided tvbuff coincides
3230 If the dissector discovers that the end of the tvbuff does /not/ coincide with
3231 the end of a PDU, (ie, there is half of a PDU at the end of the tvbuff), it can
3233 desegment_offset field is the offset in the tvbuff at which the dissector will
3236 time your dissect_PROTO is called, it will be passed a tvbuff composed of the
3237 end of the data from the previous tvbuff together with desegment_len more bytes.
3294 requesting more data until the tvbuff contains a complete C string. The C string
3296 than one complete C string in the tvbuff, so the dissection is done in a
3351 the tvbuff pointer, packet_info pointer, and proto_tree pointer
3358 packet_info pointer, a tvbuff pointer and an offset value representing the
3359 offset into the tvbuff at which a PDU begins, and a void pointer for user
3366 a routine that takes as arguments a packet_info pointer, a tvbuff
3367 pointer and an offset value representing the offset into the tvbuff
3376 a new_dissector_t routine to dissect the pdu that's passed a tvbuff
3378 user data, with the tvbuff containing a possibly-reassembled PDU. (The
3379 "reported_length" of the tvbuff will be the length of the PDU);
3457 The ptvcursor API lets you extract data from a tvbuff, and add it to a
3459 tvbuff so that you can extract data again without having to compute any
3486 This creates a new ptvcursor_t object for iterating over a tvbuff.
3492 This will extract 'length' bytes from the tvbuff and place it in
3558 Returns the tvbuff associated with the ptvcursor.