wireshark/packaging/debian/libwsutil0.symbols

471 lines
14 KiB
Plaintext
Raw Normal View History

libwsutil.so.0 libwsutil0 #MINVER#
Dot11DecryptWepDecrypt@Base 2.5.0
Eax_Decrypt@Base 1.12.0~rc1
adler32_bytes@Base 1.12.0~rc1
adler32_str@Base 1.12.0~rc1
alaw2linear@Base 1.12.0~rc1
allowed_profile_filenames@Base 3.1.1
ascii_strdown_inplace@Base 1.10.0
ascii_strup_inplace@Base 1.10.0
bitswap_buf_inplace@Base 1.12.0~rc1
bytes_to_hexstr@Base 3.5.0
bytes_to_hexstr_punct@Base 3.5.0
bytes_to_str_maxlen@Base 3.7.0
bytes_to_str_punct_maxlen@Base 3.7.0
codec_decode@Base 3.1.0
codec_get_channels@Base 3.1.0
codec_get_frequency@Base 3.1.0
codec_init@Base 3.1.0
codec_release@Base 3.1.0
codecs_cleanup@Base 3.1.0
codecs_init@Base 3.1.0
codecs_register_plugin@Base 3.1.0
config_file_exists_with_entries@Base 2.9.0
configuration_init@Base 3.7.0
copy_file_binary_mode@Base 1.12.0~rc1
copy_persconffile_profile@Base 1.12.0~rc1
crc11_307_noreflect_noxor@Base 1.10.0
crc16_0x080F_seed@Base 2.3.0
crc16_0x3D65_seed@Base 1.99.0
crc16_0x5935@Base 1.10.0
crc16_0x755B@Base 1.12.0~rc1
crc16_0x9949_seed@Base 1.12.0~rc1
crc16_8005_noreflect_noxor@Base 1.10.0
crc16_ccitt@Base 1.10.0
crc16_ccitt_seed@Base 1.10.0
crc16_iso14443a@Base 2.1.0
crc16_plain_update@Base 1.10.0
crc16_usb@Base 3.1.0
crc16_x25_ccitt_seed@Base 1.99.3
crc32_0x5D6DCB_seed@Base 2.3.0
crc32_0x0AA725CF_seed@Base 1.12.0~rc1
crc32_ccitt@Base 1.10.0
crc32_ccitt_seed@Base 1.10.0
crc32_ccitt_table_lookup@Base 1.10.0
crc32_mpeg2_seed@Base 1.10.0
crc32c_calculate@Base 1.10.0
crc32c_calculate_no_swap@Base 1.10.0
crc32c_table_lookup@Base 1.10.0
crc5_usb_11bit_input@Base 3.1.1
crc5_usb_19bit_input@Base 3.1.1
crc6_0X6F@Base 1.12.0~rc1
crc7update@Base 1.10.0
crc8_0x2F@Base 1.10.0
crc8_0x37@Base 2.3.0
crc8_0x3B@Base 2.3.0
create_persconffile_dir@Base 1.12.0~rc1
create_persconffile_profile@Base 1.12.0~rc1
create_profiles_dir@Base 2.5.0
create_tempfile@Base 1.12.0~rc1
create_timestamp@Base 2.5.0
crypt_des_ecb@Base 2.3.0
crypto_scalarmult_curve25519@Base 2.9.0
crypto_scalarmult_curve25519_base@Base 2.9.0
data_file_url@Base 2.3.0
2022-03-11 07:28:12 +00:00
decode_synchsafe_int@Base 3.7.0
decrypt_xtea_ecb@Base 2.5.0
decrypt_xtea_le_ecb@Base 2.5.0
delete_persconffile_profile@Base 1.12.0~rc1
deregister_codec@Base 3.1.0
2021-09-16 17:23:47 +00:00
dword_to_hex@Base 3.5.1
dword_to_hex_punct@Base 3.5.1
2021-09-16 22:13:41 +00:00
eui64_to_str@Base 3.5.1
file_exists@Base 1.12.0~rc1
file_needs_reopen@Base 3.0.6
file_open_error_message@Base 1.12.0~rc1
file_write_error_message@Base 1.12.0~rc1
files_identical@Base 1.12.0~rc1
filetime_to_nstime@Base 2.0.0
find_codec@Base 3.1.0
find_last_pathname_separator@Base 1.12.0~rc1
format_size_wmem@Base 3.5.0
2022-09-29 08:27:00 +00:00
format_text@Base 4.1.0
format_text_chr@Base 4.1.0
format_text_string@Base 4.1.0
format_text_wsp@Base 4.1.0
free_features@Base 3.7.0
free_progdirs@Base 2.3.0
get_basename@Base 1.12.0~rc1
get_configuration_namespace@Base 3.7.0
get_cur_groupname@Base 1.10.0
get_cur_username@Base 1.10.0
get_cpu_info@Base 2.3.0
get_datafile_dir@Base 1.12.0~rc1
get_datafile_path@Base 1.12.0~rc1
get_dirname@Base 1.12.0~rc1
get_extcap_dir@Base 1.99.0
get_friendly_program_name@Base 3.5.0
get_global_profiles_dir@Base 1.12.0~rc1
get_os_version_info@Base 1.99.0
get_persconffile_path@Base 1.12.0~rc1
get_persdatafile_dir@Base 1.12.0~rc1
get_plugins_dir@Base 2.5.0
get_plugins_dir_with_version@Base 2.5.0
get_plugins_pers_dir@Base 1.12.0~rc1
get_plugins_pers_dir_with_version@Base 2.5.0
get_profile_dir@Base 2.9.0
get_profile_name@Base 1.12.0~rc1
get_profiles_dir@Base 1.12.0~rc1
get_progfile_dir@Base 1.12.0~rc1
get_resource_usage@Base 2.3.0
get_systemfile_dir@Base 1.12.0~rc1
2021-09-16 22:13:41 +00:00
guint32_to_str_buf@Base 3.5.1
guint64_to_str_buf@Base 3.5.1
2021-09-16 17:23:47 +00:00
guint8_to_hex@Base 3.5.1
has_global_profiles@Base 1.12.0~rc1
2021-09-15 18:15:22 +00:00
hex64_to_str_back_len@Base 3.5.1
hex_to_str_back_len@Base 3.5.1
hkdf_expand@Base 2.5.1
ieee80211_chan_to_mhz@Base 1.99.7
ieee80211_mhz_to_chan@Base 1.99.7
ieee80211_mhz_to_str@Base 1.99.7
init_process_policies@Base 1.10.0
init_report_message@Base 2.3.0
2021-09-15 18:15:22 +00:00
int64_to_str_back@Base 3.5.1
int_to_str_back@Base 3.5.1
2021-09-16 22:13:41 +00:00
ip6_to_str@Base 3.5.1
ip6_to_str_buf@Base 3.5.1
ip_to_str@Base 3.5.1
ip_to_str_buf@Base 3.5.1
ipxnet_to_str_punct@Base 3.5.1
is_default_profile@Base 1.12.0~rc1
2022-07-08 01:16:41 +00:00
is_packet_configuration_namespace@Base 3.7.2
isdigit_string@Base 1.10.0
iso8601_to_nstime@Base 3.5.0
isprint_string@Base 1.10.0
isprint_utf8_string@Base 2.6.1
json_decode_string_inplace@Base 2.9.0
Replace JSON-GLib by custom JSON dumper library The (optional) JSON-GLib library adds dependencies on GObject, GIO. For statically linked oss-fuzz builds it also adds libffi and more. To avoid these dependencies, replace JSON-GLib by some custom code. This allows `tshark -G elastic-mapping` to be enabled by default without extra deps. API design goals of the new JSON dumper library: - Small interface without a lot of abstraction. - Avoid memory allocations if possible (currently none, but maybe json_puts_string will be replaced to improve UTF-8 support). - Do not implement parsing, this is currently handled by jsmn. Methods to open/close array/objects and to set members are inspired by the JsonGlib interface. The interfaces to write values is inspired by the sharkd code (json_puts_string is also borrowed from that). The only observed differences in the tshark output: - JSON-GLib ignores duplicates, json_dumper does not and may produce duplicates and currently print two "ip.opt.sec_prot_auth_unassigned". - JSON-GLib adds a space before a colon (unimportant formatting detail). - (Not observed, but UTF-8 strings will be wrong like bug 14948.) A test was added to catch changes in the tshark output. I also fuzzed json_dumper with libFuzzer + UBSAN/ASAN and fixed an off-by-one error. Change-Id: I0c85b18777b04d1e0f613a3d59935ec59be87ff4 Link: https://www.wireshark.org/lists/wireshark-dev/201811/msg00052.html Reviewed-on: https://code.wireshark.org/review/30732 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-11-20 01:47:36 +00:00
json_dumper_begin_array@Base 2.9.0
json_dumper_begin_base64@Base 2.9.1
Replace JSON-GLib by custom JSON dumper library The (optional) JSON-GLib library adds dependencies on GObject, GIO. For statically linked oss-fuzz builds it also adds libffi and more. To avoid these dependencies, replace JSON-GLib by some custom code. This allows `tshark -G elastic-mapping` to be enabled by default without extra deps. API design goals of the new JSON dumper library: - Small interface without a lot of abstraction. - Avoid memory allocations if possible (currently none, but maybe json_puts_string will be replaced to improve UTF-8 support). - Do not implement parsing, this is currently handled by jsmn. Methods to open/close array/objects and to set members are inspired by the JsonGlib interface. The interfaces to write values is inspired by the sharkd code (json_puts_string is also borrowed from that). The only observed differences in the tshark output: - JSON-GLib ignores duplicates, json_dumper does not and may produce duplicates and currently print two "ip.opt.sec_prot_auth_unassigned". - JSON-GLib adds a space before a colon (unimportant formatting detail). - (Not observed, but UTF-8 strings will be wrong like bug 14948.) A test was added to catch changes in the tshark output. I also fuzzed json_dumper with libFuzzer + UBSAN/ASAN and fixed an off-by-one error. Change-Id: I0c85b18777b04d1e0f613a3d59935ec59be87ff4 Link: https://www.wireshark.org/lists/wireshark-dev/201811/msg00052.html Reviewed-on: https://code.wireshark.org/review/30732 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-11-20 01:47:36 +00:00
json_dumper_begin_object@Base 2.9.0
json_dumper_end_array@Base 2.9.0
json_dumper_end_base64@Base 2.9.1
Replace JSON-GLib by custom JSON dumper library The (optional) JSON-GLib library adds dependencies on GObject, GIO. For statically linked oss-fuzz builds it also adds libffi and more. To avoid these dependencies, replace JSON-GLib by some custom code. This allows `tshark -G elastic-mapping` to be enabled by default without extra deps. API design goals of the new JSON dumper library: - Small interface without a lot of abstraction. - Avoid memory allocations if possible (currently none, but maybe json_puts_string will be replaced to improve UTF-8 support). - Do not implement parsing, this is currently handled by jsmn. Methods to open/close array/objects and to set members are inspired by the JsonGlib interface. The interfaces to write values is inspired by the sharkd code (json_puts_string is also borrowed from that). The only observed differences in the tshark output: - JSON-GLib ignores duplicates, json_dumper does not and may produce duplicates and currently print two "ip.opt.sec_prot_auth_unassigned". - JSON-GLib adds a space before a colon (unimportant formatting detail). - (Not observed, but UTF-8 strings will be wrong like bug 14948.) A test was added to catch changes in the tshark output. I also fuzzed json_dumper with libFuzzer + UBSAN/ASAN and fixed an off-by-one error. Change-Id: I0c85b18777b04d1e0f613a3d59935ec59be87ff4 Link: https://www.wireshark.org/lists/wireshark-dev/201811/msg00052.html Reviewed-on: https://code.wireshark.org/review/30732 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-11-20 01:47:36 +00:00
json_dumper_end_object@Base 2.9.0
json_dumper_finish@Base 2.9.0
json_dumper_set_member_name@Base 2.9.0
json_dumper_value_anyf@Base 2.9.0
json_dumper_value_double@Base 3.0.0
Replace JSON-GLib by custom JSON dumper library The (optional) JSON-GLib library adds dependencies on GObject, GIO. For statically linked oss-fuzz builds it also adds libffi and more. To avoid these dependencies, replace JSON-GLib by some custom code. This allows `tshark -G elastic-mapping` to be enabled by default without extra deps. API design goals of the new JSON dumper library: - Small interface without a lot of abstraction. - Avoid memory allocations if possible (currently none, but maybe json_puts_string will be replaced to improve UTF-8 support). - Do not implement parsing, this is currently handled by jsmn. Methods to open/close array/objects and to set members are inspired by the JsonGlib interface. The interfaces to write values is inspired by the sharkd code (json_puts_string is also borrowed from that). The only observed differences in the tshark output: - JSON-GLib ignores duplicates, json_dumper does not and may produce duplicates and currently print two "ip.opt.sec_prot_auth_unassigned". - JSON-GLib adds a space before a colon (unimportant formatting detail). - (Not observed, but UTF-8 strings will be wrong like bug 14948.) A test was added to catch changes in the tshark output. I also fuzzed json_dumper with libFuzzer + UBSAN/ASAN and fixed an off-by-one error. Change-Id: I0c85b18777b04d1e0f613a3d59935ec59be87ff4 Link: https://www.wireshark.org/lists/wireshark-dev/201811/msg00052.html Reviewed-on: https://code.wireshark.org/review/30732 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-11-20 01:47:36 +00:00
json_dumper_value_string@Base 2.9.0
json_dumper_value_va_list@Base 2.9.1
json_dumper_write_base64@Base 2.9.1
json_get_array@Base 3.5.0
json_get_array_index@Base 3.5.0
json_get_array_len@Base 3.5.0
json_get_double@Base 3.1.0
json_get_object@Base 3.1.0
json_get_string@Base 3.1.0
json_parse@Base 2.9.0
json_validate@Base 2.9.0
linear2alaw@Base 1.12.0~rc1
linear2ulaw@Base 1.12.0~rc1
local_interfaces_to_list@Base 2.1.2
log_resource_usage@Base 2.1.2
mktime_utc@Base 1.12.0~rc1
mpa_bitrate@Base 1.10.0
mpa_frequency@Base 1.10.0
mpa_layer@Base 1.10.0
mpa_padding@Base 1.10.0
mpa_samples@Base 1.10.0
mpa_version@Base 1.10.0
nsfiletime_to_nstime@Base 2.0.0
nstime_cmp@Base 1.12.0~rc1
nstime_copy@Base 1.12.0~rc1
nstime_delta@Base 1.12.0~rc1
nstime_is_unset@Base 1.12.0~rc1
nstime_is_zero@Base 1.12.0~rc1
nstime_set_unset@Base 1.12.0~rc1
nstime_set_zero@Base 1.12.0~rc1
nstime_sum@Base 1.12.0~rc1
nstime_to_msec@Base 1.12.0~rc1
nstime_to_sec@Base 1.12.0~rc1
2021-09-15 18:15:22 +00:00
oct64_to_str_back@Base 3.5.1
oct_to_str_back@Base 3.5.1
please_report_bug@Base 3.1.0
please_report_bug_short@Base 3.1.0
plugins_cleanup@Base 2.3.0
plugins_dump_all@Base 1.12.0~rc1
plugins_get_count@Base 2.5.0
plugins_get_descriptions@Base 1.12.0~rc1
printable_char_or_period@Base 1.99.0
profile_exists@Base 1.12.0~rc1
profile_register_persconffile@Base 3.5.1
profile_store_persconffiles@Base 1.12.0~rc1
2021-09-16 17:23:47 +00:00
qword_to_hex@Base 3.5.1
qword_to_hex_punct@Base 3.5.1
register_codec@Base 3.1.0
relinquish_special_privs_perm@Base 1.10.0
rename_persconffile_profile@Base 1.12.0~rc1
report_cfile_close_failure@Base 3.5.0
report_cfile_dump_open_failure@Base 3.5.0
report_cfile_open_failure@Base 3.5.0
report_cfile_read_failure@Base 3.5.0
report_cfile_write_failure@Base 3.5.0
report_failure@Base 1.12.0~rc1
report_open_failure@Base 1.12.0~rc1
report_read_failure@Base 1.12.0~rc1
report_warning@Base 2.3.0
report_write_failure@Base 1.12.0~rc1
rsa_load_pem_key@Base 2.5.0
rsa_load_pkcs12@Base 2.5.0
rsa_decrypt_inplace@Base 2.5.0
rsa_private_key_free@Base 2.5.0
rsa_privkey_to_sexp@Base 2.5.0
running_in_build_directory@Base 1.12.0~rc1
running_with_special_privs@Base 1.10.0
plugins_init@Base 2.5.0
set_persconffile_dir@Base 1.12.0~rc1
set_persdatafile_dir@Base 1.12.0~rc1
set_profile_name@Base 1.12.0~rc1
sober128_add_entropy@Base 1.99.0
sober128_read@Base 1.99.0
sober128_start@Base 1.99.0
sort_features@Base 3.7.0
started_with_special_privs@Base 1.10.0
test_for_directory@Base 1.12.0~rc1
test_for_fifo@Base 1.12.0~rc1
tm_is_valid@Base 3.5.0
type_util_gdouble_to_guint64@Base 1.10.0
type_util_guint64_to_gdouble@Base 1.10.0
2021-09-15 18:15:22 +00:00
uint64_to_str_back@Base 3.5.1
uint64_to_str_back_len@Base 3.5.1
uint_to_str_back@Base 3.5.1
uint_to_str_back_len@Base 3.5.1
ulaw2linear@Base 1.12.0~rc1
editcap: add support for epoch timestamps in `-A` and `-B` options Inspired in https://gitlab.com/wireshark/wireshark/-/merge_requests/1618. Tested: Timestamps on file used for comparison: ``` $ tshark -r test/captures/snakeoil-dtls.pcap -T fields -e frame.time_epoch 1150121069.248818000 1150121069.249193000 1150121069.251152000 1150121069.251384000 1150121069.293686000 1150121069.319315000 1150121075.230753000 1150121105.510885000 1150121105.510934000 ``` Before: ``` $ ./build/run/editcap -B 1150121069.3 test/captures/snakeoil-dtls.pcap - editcap: "1150121069.3" isn't a valid date and time $ ./build/run/editcap -A 1150121069.3 test/captures/snakeoil-dtls.pcap - editcap: "1150121069.3" isn't a valid date and time $ ./build/run/editcap -A 1150121069 test/captures/snakeoil-dtls.pcap - editcap: "1150121069" isn't a valid date and time $ ./build/run/editcap -B 1150121069 test/captures/snakeoil-dtls.pcap - editcap: "1150121069" isn't a valid date and time ``` After: ``` $ ./build/run/editcap -A 1150121069.3 test/captures/snakeoil-dtls.pcap - | tshark -r - -T fields -e frame.time_epoch 1150121069.319315000 1150121075.230753000 1150121105.510885000 1150121105.510934000 $ ./build/run/editcap -A 1150121069 test/captures/snakeoil-dtls.pcap - | tshark -r - -T fields -e frame.time_epoch 1150121069.248818000 1150121069.249193000 1150121069.251152000 1150121069.251384000 1150121069.293686000 1150121069.319315000 1150121075.230753000 1150121105.510885000 1150121105.510934000 $ ./build/run/editcap -B 1150121069.3 test/captures/snakeoil-dtls.pcap - | tshark -r - -T fields -e frame.time_epoch 1150121069.248818000 1150121069.249193000 1150121069.251152000 1150121069.251384000 1150121069.293686000 $ ./build/run/editcap -B 1150121069 test/captures/snakeoil-dtls.pcap - | tshark -r - -T fields -e frame.time_epoch ```
2020-11-02 21:51:36 +00:00
unix_epoch_to_nstime@Base 3.5.0
update_adler32@Base 1.12.0~rc1
update_crc10_by_bytes@Base 1.10.0
with_feature@Base 3.7.0
without_feature@Base 3.7.0
wmem_alloc0@Base 3.5.0
wmem_alloc@Base 3.5.0
wmem_allocator_new@Base 3.5.0
wmem_array_append@Base 3.5.0
wmem_array_bzero@Base 3.5.0
wmem_array_get_count@Base 3.5.0
wmem_array_get_raw@Base 3.5.0
wmem_array_grow@Base 3.5.0
wmem_array_index@Base 3.5.0
wmem_array_new@Base 3.5.0
wmem_array_set_null_terminator@Base 3.5.0
wmem_array_sized_new@Base 3.5.0
wmem_array_sort@Base 3.5.0
wmem_array_try_index@Base 3.5.0
wmem_ascii_strdown@Base 3.5.0
wmem_cleanup@Base 3.5.0
2021-11-27 17:31:16 +00:00
wmem_compare_int@Base 3.7.0
wmem_compare_uint@Base 3.7.0
wmem_destroy_allocator@Base 3.5.0
wmem_destroy_array@Base 3.5.0
wmem_destroy_list@Base 3.5.0
wmem_double_hash@Base 3.5.0
wmem_enter_scope@Base 3.5.0
wmem_free@Base 3.5.0
wmem_free_all@Base 3.5.0
wmem_gc@Base 3.5.0
wmem_in_scope@Base 3.5.0
wmem_init@Base 3.5.0
wmem_int64_hash@Base 3.5.0
wmem_itree_find_intervals@Base 3.5.0
wmem_itree_insert@Base 3.5.0
wmem_itree_is_empty@Base 3.5.0
wmem_itree_new@Base 3.5.0
wmem_leave_scope@Base 3.5.0
wmem_list_append@Base 3.5.0
wmem_list_count@Base 3.5.0
wmem_list_find@Base 3.5.0
wmem_list_find_custom@Base 3.5.0
wmem_list_foreach@Base 3.5.0
wmem_list_frame_data@Base 3.5.0
wmem_list_frame_next@Base 3.5.0
wmem_list_frame_prev@Base 3.5.0
wmem_list_head@Base 3.5.0
wmem_list_insert_sorted@Base 3.5.0
wmem_list_new@Base 3.5.0
wmem_list_prepend@Base 3.5.0
wmem_list_remove@Base 3.5.0
wmem_list_remove_frame@Base 3.5.0
wmem_list_tail@Base 3.5.0
wmem_map_contains@Base 3.5.0
wmem_map_foreach@Base 3.5.0
wmem_map_foreach_remove@Base 4.1.0
wmem_map_get_keys@Base 3.5.0
wmem_map_insert@Base 3.5.0
wmem_map_lookup@Base 3.5.0
wmem_map_lookup_extended@Base 3.5.0
wmem_map_new@Base 3.5.0
wmem_map_new_autoreset@Base 3.5.0
wmem_map_remove@Base 3.5.0
wmem_map_size@Base 3.5.0
wmem_map_steal@Base 3.5.0
wmem_memdup@Base 3.5.0
wmem_multimap_count@Base 3.7.0
wmem_multimap_get_keys@Base 3.7.0
wmem_multimap_insert32@Base 3.7.0
wmem_multimap_lookup32@Base 3.7.0
wmem_multimap_lookup32_le@Base 3.7.0
wmem_multimap_new@Base 3.7.0
wmem_multimap_new_autoreset@Base 3.7.0
wmem_multimap_remove32@Base 3.7.0
wmem_multimap_size@Base 3.7.0
2021-12-06 16:06:13 +00:00
wmem_print_tree@Base 3.7.0
wmem_realloc@Base 3.5.0
wmem_register_callback@Base 3.5.0
wmem_stack_peek@Base 3.5.0
wmem_stack_pop@Base 3.5.0
wmem_str_hash@Base 3.5.0
wmem_strbuf_append@Base 3.5.0
wmem_strbuf_append_c@Base 3.5.0
2022-10-06 09:44:52 +00:00
wmem_strbuf_append_hex@Base 4.1.0rc0-393-gb2cbc6f034d6
wmem_strbuf_append_len@Base 3.5.0
wmem_strbuf_append_printf@Base 3.5.0
wmem_strbuf_append_unichar@Base 3.5.0
wmem_strbuf_append_vprintf@Base 3.5.0
wmem_strbuf_destroy@Base 3.5.0
2022-06-21 17:03:04 +00:00
wmem_strbuf_dup@Base 3.7.1rc0-272-gfe25d701baa2
wmem_strbuf_finalize@Base 3.5.0
wmem_strbuf_get_len@Base 3.5.0
wmem_strbuf_get_str@Base 3.5.0
wmem_strbuf_new@Base 3.5.0
2022-06-21 17:03:04 +00:00
wmem_strbuf_new_len@Base 3.7.1rc0-272-gfe25d701baa2
wmem_strbuf_sized_new@Base 3.5.0
2022-06-21 17:03:04 +00:00
wmem_strbuf_strcmp@Base 3.7.1rc0-272-gfe25d701baa2
wmem_strbuf_strstr@Base 3.7.1rc0-272-gfe25d701baa2
2022-10-06 09:44:52 +00:00
wmem_strbuf_utf8_make_valid@Base 4.1.0rc0-393-gb2cbc6f034d6
wmem_strbuf_utf8_validate@Base 4.1.0rc0-393-gb2cbc6f034d6
wmem_strbuf_truncate@Base 3.5.0
wmem_strconcat@Base 3.5.0
wmem_strdup@Base 3.5.0
wmem_strdup_printf@Base 3.5.0
wmem_strdup_vprintf@Base 3.5.0
wmem_strjoin@Base 3.5.0
wmem_strjoinv@Base 3.5.0
wmem_strndup@Base 3.5.0
wmem_strong_hash@Base 3.5.0
wmem_strsplit@Base 3.5.0
wmem_tree_contains32@Base 4.1.0
wmem_tree_count@Base 3.5.0
wmem_tree_destroy@Base 3.5.0
wmem_tree_foreach@Base 3.5.0
wmem_tree_insert32@Base 3.5.0
wmem_tree_insert32_array@Base 3.5.0
wmem_tree_insert_string@Base 3.5.0
wmem_tree_is_empty@Base 3.5.0
wmem_tree_lookup32@Base 3.5.0
wmem_tree_lookup32_array@Base 3.5.0
wmem_tree_lookup32_array_le@Base 3.5.0
wmem_tree_lookup32_le@Base 3.5.0
wmem_tree_lookup_string@Base 3.5.0
wmem_tree_new@Base 3.5.0
wmem_tree_new_autoreset@Base 3.5.0
wmem_tree_remove_string@Base 3.5.0
wmem_tree_remove32@Base 3.5.0
wmem_unregister_callback@Base 3.5.0
2021-09-16 17:23:47 +00:00
word_to_hex@Base 3.5.1
word_to_hex_npad@Base 3.5.1
word_to_hex_punct@Base 3.5.1
write_file_binary_mode@Base 3.5.0
ws_add_crash_info@Base 1.10.0
ws_ascii_strnatcasecmp@Base 1.99.1
ws_ascii_strnatcmp@Base 1.99.1
ws_base32_decode@Base 2.3.0
ws_basestrtou16@Base 2.9.0
ws_basestrtou32@Base 2.9.0
ws_basestrtou64@Base 2.9.0
ws_basestrtou8@Base 2.9.0
ws_basestrtou@Base 3.3.0
ws_buffer_append@Base 1.99.0
ws_buffer_assure_space@Base 1.99.0
ws_buffer_free@Base 1.99.0
ws_buffer_init@Base 1.99.0
ws_buffer_remove_start@Base 1.99.0
ws_cleanup_sockets@Base 3.1.0
ws_clock_get_realtime@Base 3.7.0
ws_cmac_buffer@Base 3.1.0
2022-10-07 15:14:52 +00:00
ws_enums_bsearch@Base 4.1.0rc0-408-gda4277971fe0
2022-06-21 17:03:04 +00:00
ws_escape_null@Base 3.7.1rc0-272-gfe25d701baa2
2021-11-29 17:23:17 +00:00
ws_escape_string@Base 3.7.0
2022-06-21 17:03:04 +00:00
ws_escape_string_len@Base 3.7.1rc0-272-gfe25d701baa2
ws_getopt@Base 3.5.1
ws_getopt_long@Base 3.5.1
ws_getopt_long_only@Base 3.5.1
ws_buffer_cleanup@Base 2.3.0
ws_hexstrtou16@Base 2.3.0
ws_hexstrtou32@Base 2.3.0
ws_hexstrtou64@Base 2.3.0
ws_hexstrtou8@Base 2.3.0
ws_hexstrtou@Base 3.3.0
ws_hmac_buffer@Base 2.3.0
ws_inet_ntop4@Base 2.1.2
ws_inet_ntop6@Base 2.1.2
ws_inet_pton4@Base 2.1.2
ws_inet_pton6@Base 2.1.2
ws_init_sockets@Base 3.1.0
Refactor our logging and extend the wslog API Experience has shown that: 1. The current logging methods are not very reliable or practical. A logging bitmask makes little sense as the user-facing interface (who would want debug but not crtical messages for example?); it's computer-friendly and user-unfriendly. More importantly the console log level preference is initialized too late in the startup process to be used for the logging subsystem and that fact raises a number of annoying and hard-to-fix usability issues. 2. Coding around G_MESSAGES_DEBUG to comply with our log level mask and not clobber the user's settings or not create unexpected log misses is unworkable and generally follows the principle of most surprise. The fact that G_MESSAGES_DEBUG="all" can leak to other programs using GLib is also annoying. 3. The non-structured GLib logging API is very opinionated and lacks configurability beyond replacing the log handler. 4. Windows GUI has some special code to attach to a console, but it would be nice to abstract away the rest under a single interface. 5. Using this logger seems to be noticeably faster. Deprecate the console log level preference and extend our API to implement a log handler in wsutil/wslog.h to provide easy-to-use, flexible and dependable logging during all execution phases. Log levels have a hierarchy, from most verbose to least verbose (debug to error). When a given level is set everything above that is also enabled. The log level can be set with an environment variable or a command line option (parsed as soon as possible but still later than the environment). The default log level is "message". Dissector logging is not included because it is not clear what log domain they should use. An explosion to thousands of domains is not desirable and putting everything in a single domain is probably too coarse and noisy. For now I think it makes sense to let them do their own thing using g_log_default_handler() and continue using the G_MESSAGES_DEBUG mechanism with specific domains for each individual dissector. In the future a mechanism may be added to selectively enable these domains at runtime while trying to avoid the problems introduced by G_MESSAGES_DEBUG.
2021-06-08 01:46:52 +00:00
ws_log@Base 3.5.0
ws_log_add_custom_file@Base 3.5.0
ws_log_buffer_full@Base 3.5.1
ws_log_console_writer@Base 3.7.0
ws_log_console_writer_set_use_stdout@Base 3.7.0
2022-01-04 12:20:21 +00:00
ws_log_fatal_full@Base 3.7.0
ws_log_file_writer@Base 3.7.0
ws_log_full@Base 3.5.0
Refactor our logging and extend the wslog API Experience has shown that: 1. The current logging methods are not very reliable or practical. A logging bitmask makes little sense as the user-facing interface (who would want debug but not crtical messages for example?); it's computer-friendly and user-unfriendly. More importantly the console log level preference is initialized too late in the startup process to be used for the logging subsystem and that fact raises a number of annoying and hard-to-fix usability issues. 2. Coding around G_MESSAGES_DEBUG to comply with our log level mask and not clobber the user's settings or not create unexpected log misses is unworkable and generally follows the principle of most surprise. The fact that G_MESSAGES_DEBUG="all" can leak to other programs using GLib is also annoying. 3. The non-structured GLib logging API is very opinionated and lacks configurability beyond replacing the log handler. 4. Windows GUI has some special code to attach to a console, but it would be nice to abstract away the rest under a single interface. 5. Using this logger seems to be noticeably faster. Deprecate the console log level preference and extend our API to implement a log handler in wsutil/wslog.h to provide easy-to-use, flexible and dependable logging during all execution phases. Log levels have a hierarchy, from most verbose to least verbose (debug to error). When a given level is set everything above that is also enabled. The log level can be set with an environment variable or a command line option (parsed as soon as possible but still later than the environment). The default log level is "message". Dissector logging is not included because it is not clear what log domain they should use. An explosion to thousands of domains is not desirable and putting everything in a single domain is probably too coarse and noisy. For now I think it makes sense to let them do their own thing using g_log_default_handler() and continue using the G_MESSAGES_DEBUG mechanism with specific domains for each individual dissector. In the future a mechanism may be added to selectively enable these domains at runtime while trying to avoid the problems introduced by G_MESSAGES_DEBUG.
2021-06-08 01:46:52 +00:00
ws_log_get_level@Base 3.5.0
ws_log_init@Base 3.5.0
ws_log_init_with_writer@Base 3.5.0
ws_log_init_with_writer_and_data@Base 3.5.0
Refactor our logging and extend the wslog API Experience has shown that: 1. The current logging methods are not very reliable or practical. A logging bitmask makes little sense as the user-facing interface (who would want debug but not crtical messages for example?); it's computer-friendly and user-unfriendly. More importantly the console log level preference is initialized too late in the startup process to be used for the logging subsystem and that fact raises a number of annoying and hard-to-fix usability issues. 2. Coding around G_MESSAGES_DEBUG to comply with our log level mask and not clobber the user's settings or not create unexpected log misses is unworkable and generally follows the principle of most surprise. The fact that G_MESSAGES_DEBUG="all" can leak to other programs using GLib is also annoying. 3. The non-structured GLib logging API is very opinionated and lacks configurability beyond replacing the log handler. 4. Windows GUI has some special code to attach to a console, but it would be nice to abstract away the rest under a single interface. 5. Using this logger seems to be noticeably faster. Deprecate the console log level preference and extend our API to implement a log handler in wsutil/wslog.h to provide easy-to-use, flexible and dependable logging during all execution phases. Log levels have a hierarchy, from most verbose to least verbose (debug to error). When a given level is set everything above that is also enabled. The log level can be set with an environment variable or a command line option (parsed as soon as possible but still later than the environment). The default log level is "message". Dissector logging is not included because it is not clear what log domain they should use. An explosion to thousands of domains is not desirable and putting everything in a single domain is probably too coarse and noisy. For now I think it makes sense to let them do their own thing using g_log_default_handler() and continue using the G_MESSAGES_DEBUG mechanism with specific domains for each individual dissector. In the future a mechanism may be added to selectively enable these domains at runtime while trying to avoid the problems introduced by G_MESSAGES_DEBUG.
2021-06-08 01:46:52 +00:00
ws_log_level_to_string@Base 3.5.0
ws_log_msg_is_active@Base 3.5.0
ws_log_parse_args@Base 3.5.0
2021-06-15 21:50:46 +00:00
ws_log_print_usage@Base 3.5.0
ws_log_set_debug_filter@Base 3.5.0
ws_log_set_domain_filter@Base 3.5.0
ws_log_set_noisy_filter@Base 3.5.0
ws_log_set_fatal_domain_filter@Base 4.1.0
ws_log_set_fatal_level@Base 4.1.0
ws_log_set_fatal_level_str@Base 4.1.0
Refactor our logging and extend the wslog API Experience has shown that: 1. The current logging methods are not very reliable or practical. A logging bitmask makes little sense as the user-facing interface (who would want debug but not crtical messages for example?); it's computer-friendly and user-unfriendly. More importantly the console log level preference is initialized too late in the startup process to be used for the logging subsystem and that fact raises a number of annoying and hard-to-fix usability issues. 2. Coding around G_MESSAGES_DEBUG to comply with our log level mask and not clobber the user's settings or not create unexpected log misses is unworkable and generally follows the principle of most surprise. The fact that G_MESSAGES_DEBUG="all" can leak to other programs using GLib is also annoying. 3. The non-structured GLib logging API is very opinionated and lacks configurability beyond replacing the log handler. 4. Windows GUI has some special code to attach to a console, but it would be nice to abstract away the rest under a single interface. 5. Using this logger seems to be noticeably faster. Deprecate the console log level preference and extend our API to implement a log handler in wsutil/wslog.h to provide easy-to-use, flexible and dependable logging during all execution phases. Log levels have a hierarchy, from most verbose to least verbose (debug to error). When a given level is set everything above that is also enabled. The log level can be set with an environment variable or a command line option (parsed as soon as possible but still later than the environment). The default log level is "message". Dissector logging is not included because it is not clear what log domain they should use. An explosion to thousands of domains is not desirable and putting everything in a single domain is probably too coarse and noisy. For now I think it makes sense to let them do their own thing using g_log_default_handler() and continue using the G_MESSAGES_DEBUG mechanism with specific domains for each individual dissector. In the future a mechanism may be added to selectively enable these domains at runtime while trying to avoid the problems introduced by G_MESSAGES_DEBUG.
2021-06-08 01:46:52 +00:00
ws_log_set_level@Base 3.5.0
ws_log_set_level_str@Base 3.5.0
2021-12-05 18:19:34 +00:00
ws_log_set_writer@Base 3.7.0
ws_log_set_writer_with_data@Base 3.7.0
2022-10-06 09:44:52 +00:00
ws_log_utf8_full@Base 4.1.0
ws_log_write_always_full@Base 3.5.0
Refactor our logging and extend the wslog API Experience has shown that: 1. The current logging methods are not very reliable or practical. A logging bitmask makes little sense as the user-facing interface (who would want debug but not crtical messages for example?); it's computer-friendly and user-unfriendly. More importantly the console log level preference is initialized too late in the startup process to be used for the logging subsystem and that fact raises a number of annoying and hard-to-fix usability issues. 2. Coding around G_MESSAGES_DEBUG to comply with our log level mask and not clobber the user's settings or not create unexpected log misses is unworkable and generally follows the principle of most surprise. The fact that G_MESSAGES_DEBUG="all" can leak to other programs using GLib is also annoying. 3. The non-structured GLib logging API is very opinionated and lacks configurability beyond replacing the log handler. 4. Windows GUI has some special code to attach to a console, but it would be nice to abstract away the rest under a single interface. 5. Using this logger seems to be noticeably faster. Deprecate the console log level preference and extend our API to implement a log handler in wsutil/wslog.h to provide easy-to-use, flexible and dependable logging during all execution phases. Log levels have a hierarchy, from most verbose to least verbose (debug to error). When a given level is set everything above that is also enabled. The log level can be set with an environment variable or a command line option (parsed as soon as possible but still later than the environment). The default log level is "message". Dissector logging is not included because it is not clear what log domain they should use. An explosion to thousands of domains is not desirable and putting everything in a single domain is probably too coarse and noisy. For now I think it makes sense to let them do their own thing using g_log_default_handler() and continue using the G_MESSAGES_DEBUG mechanism with specific domains for each individual dissector. In the future a mechanism may be added to selectively enable these domains at runtime while trying to avoid the problems introduced by G_MESSAGES_DEBUG.
2021-06-08 01:46:52 +00:00
ws_logv@Base 3.5.0
2021-06-14 23:01:25 +00:00
ws_logv_full@Base 3.5.0
ws_memmem@Base 3.7.0
ws_mempbrk_compile@Base 1.99.4
ws_mempbrk_exec@Base 1.99.4
ws_optarg@Base 3.5.1
ws_opterr@Base 3.5.1
ws_optind@Base 3.5.1
ws_optopt@Base 3.5.1
ws_optpos@Base 3.5.1
ws_optreset@Base 3.5.1
ws_pipe_data_available@Base 2.5.0
ws_pipe_init@Base 2.5.1
ws_pipe_spawn_async@Base 2.5.1
ws_pipe_spawn_sync@Base 2.5.1
2021-11-12 15:55:14 +00:00
ws_regex_compile@Base 3.7.0
ws_regex_compile_ex@Base 3.7.0
2021-11-12 15:55:14 +00:00
ws_regex_free@Base 3.7.0
ws_regex_matches@Base 3.7.0
ws_regex_matches_length@Base 3.7.0
ws_regex_matches_pos@Base 3.7.2
2021-11-12 15:55:14 +00:00
ws_regex_pattern@Base 3.7.0
ws_socket_ptoa@Base 3.1.1
ws_strcasestr@Base 3.7.0
ws_strdup_underline@Base 3.7.0
ws_strerrorname_r@Base 3.7.0
ws_strptime@Base 3.7.0
ws_strtoi16@Base 2.3.0
ws_strtoi32@Base 2.3.0
ws_strtoi64@Base 2.3.0
ws_strtoi8@Base 2.3.0
ws_strtoi@Base 3.3.0
ws_strtou16@Base 2.3.0
ws_strtou32@Base 2.3.0
ws_strtou64@Base 2.3.0
ws_strtou8@Base 2.3.0
ws_strtou@Base 3.3.0
ws_utf8_char_len@Base 1.12.0~rc1
ws_vadd_crash_info@Base 2.5.2
ws_xton@Base 1.12.0~rc1