76a6e2a2bf
The ftype itself is encoding agnostic. In the case of literal display filter strings it is possible and legal to contain invalid UTF-8. Maybe it shouldn't be but that requires a user-friendly diagnostic message, not silently sanitizing the string as is done currently (only a debug message is printed in that case). Do the debug checks in proto_tree_set_string() instead. That still detects dissector code that might need fixing, which was the purpose for this check. Improve documentation and add admonition for proto_tree_add_string(). Ping #18521. |
||
|---|---|---|
| .. | ||
| .editorconfig | ||
| CMakeLists.txt | ||
| ftype-bytes.c | ||
| ftype-double.c | ||
| ftype-guid.c | ||
| ftype-ieee-11073-float.c | ||
| ftype-integer.c | ||
| ftype-ipv4.c | ||
| ftype-ipv6.c | ||
| ftype-none.c | ||
| ftype-protocol.c | ||
| ftype-string.c | ||
| ftype-time.c | ||
| ftypes-int.h | ||
| ftypes.c | ||
| ftypes.h | ||