tequilaOS/platform_system_core
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_system_core/liblog/liblog.map.txt

97 lines
2.6 KiB
Text
Raw Normal View History

Migrate liblog to ndk_library. Test: make native Bug: http://b/30465923 Change-Id: I3db7ede817a57b3505c0556ea28f08b9e8331e1a
2016-09-24 00:43:23 +02:00
LIBLOG {
global:
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
android_name_to_log_id; # llndk
android_log_id_to_name; # llndk
Migrate liblog to ndk_library. Test: make native Bug: http://b/30465923 Change-Id: I3db7ede817a57b3505c0556ea28f08b9e8331e1a
2016-09-24 00:43:23 +02:00
__android_log_assert;
Expose __android_log_buf_print and __android_log_buf_write to NDK These are needed to build libbase with the NDK. Bug: 73658597 Test: tree hugger Change-Id: Icf4a82c5c08975731c180be155743ac63f4bfd50
2018-02-20 23:45:12 +01:00
__android_log_buf_print;
__android_log_buf_write;
Migrate liblog to ndk_library. Test: make native Bug: http://b/30465923 Change-Id: I3db7ede817a57b3505c0556ea28f08b9e8331e1a
2016-09-24 00:43:23 +02:00
__android_log_print;
__android_log_vprint;
__android_log_write;
local:
*;
};
liblog: restructure log/log.h and android/log.h We went too far, so this is a partial revert, part deux. Keep general purpose logging macros in android/log.h for the NDK. More internal features like Radio, System and Events logging are moved back to log/log.h. Correct liblog ndk symbols. Correct for some Android Coding standards. Test: compile Bug: 31992412 Change-Id: Id3731496fa226e8c170305d0d2a1859e8cf67e14
2016-10-11 16:34:52 +02:00
Add LLNDK liblog stub library for the VNDK This replaces the liblog_vndk_headers with a true stub library that exports the vndk headers, and exports the vndk-specific set of symbols. Test: generated NDK stub maps are the same before/after Test: aosp_arm; m -j Test: Enable BOARD_VNDK_VERSION on aosp_arm; m -j (with other changes) Change-Id: I9037241963b3872a3bc7cf7ab36a70dd4ddcf9bc
2017-03-20 22:08:59 +01:00
LIBLOG_L {
global:
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
android_logger_clear; # llndk
android_logger_get_id; # llndk
android_logger_get_log_readable_size; # llndk
android_logger_get_log_version; # llndk
android_logger_get_log_size; # llndk
android_logger_list_alloc; # apex llndk
android_logger_list_alloc_time; # apex llndk
android_logger_list_free; # apex llndk
android_logger_list_open; # llndk
android_logger_list_read; # apex llndk
android_logger_open; # apex llndk
android_logger_set_log_size; # llndk
Add LLNDK liblog stub library for the VNDK This replaces the liblog_vndk_headers with a true stub library that exports the vndk headers, and exports the vndk-specific set of symbols. Test: generated NDK stub maps are the same before/after Test: aosp_arm; m -j Test: Enable BOARD_VNDK_VERSION on aosp_arm; m -j (with other changes) Change-Id: I9037241963b3872a3bc7cf7ab36a70dd4ddcf9bc
2017-03-20 22:08:59 +01:00
};
liblog: restructure log/log.h and android/log.h We went too far, so this is a partial revert, part deux. Keep general purpose logging macros in android/log.h for the NDK. More internal features like Radio, System and Events logging are moved back to log/log.h. Correct liblog ndk symbols. Correct for some Android Coding standards. Test: compile Bug: 31992412 Change-Id: Id3731496fa226e8c170305d0d2a1859e8cf67e14
2016-10-11 16:34:52 +02:00
LIBLOG_M {
global:
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
android_logger_get_prune_list; # llndk
android_logger_set_prune_list; # llndk
android_logger_get_statistics; # llndk
__android_log_error_write; # apex llndk
liblog: restructure log/log.h and android/log.h We went too far, so this is a partial revert, part deux. Keep general purpose logging macros in android/log.h for the NDK. More internal features like Radio, System and Events logging are moved back to log/log.h. Correct liblog ndk symbols. Correct for some Android Coding standards. Test: compile Bug: 31992412 Change-Id: Id3731496fa226e8c170305d0d2a1859e8cf67e14
2016-10-11 16:34:52 +02:00
__android_log_is_loggable;
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
create_android_logger; # apex llndk
android_log_destroy; # apex llndk
android_log_write_list_begin; # apex llndk
android_log_write_list_end; # apex llndk
android_log_write_int32; # apex llndk
android_log_write_int64; # apex llndk
android_log_write_string8; # apex llndk
android_log_write_string8_len; # apex llndk
android_log_write_float32; # apex llndk
android_log_write_list; # apex llndk
Make log_event_list.h available to vendor code. This is required in order to be able to log audit events from wpa_supplicant. Only log writing functions from log_event_list.h are made available. Test: manually Bug: 70886042 Change-Id: I097d4ad1de573662658678e6a9f1fc8f17820542
2018-02-08 20:20:56 +01:00
liblog: restructure log/log.h and android/log.h We went too far, so this is a partial revert, part deux. Keep general purpose logging macros in android/log.h for the NDK. More internal features like Radio, System and Events logging are moved back to log/log.h. Correct liblog ndk symbols. Correct for some Android Coding standards. Test: compile Bug: 31992412 Change-Id: Id3731496fa226e8c170305d0d2a1859e8cf67e14
2016-10-11 16:34:52 +02:00
};
LIBLOG_O {
global:
__android_log_is_loggable_len;
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
__android_log_is_debuggable; # apex llndk
liblog: restructure log/log.h and android/log.h We went too far, so this is a partial revert, part deux. Keep general purpose logging macros in android/log.h for the NDK. More internal features like Radio, System and Events logging are moved back to log/log.h. Correct liblog ndk symbols. Correct for some Android Coding standards. Test: compile Bug: 31992412 Change-Id: Id3731496fa226e8c170305d0d2a1859e8cf67e14
2016-10-11 16:34:52 +02:00
};
liblog: Add functions to reset log context Add android_log_parser_reset and android_log_reset to reset reader/writer log context. This allows to generate multiple log messages of the same format without context reallocation. Change-Id: Icb0f15855378aa4e66fc671ffefd15d9df6fee1e
2018-07-27 21:47:26 +02:00
Add version #29 and #30 to liblog bug: 147759770 test: build Change-Id: I38bcab9bc14088adbdbc3a92620f89a6fe397994
2020-01-15 22:58:13 +01:00
LIBLOG_Q { # introduced=29
liblog: Add functions to reset log context Add android_log_parser_reset and android_log_reset to reset reader/writer log context. This allows to generate multiple log messages of the same format without context reallocation. Change-Id: Icb0f15855378aa4e66fc671ffefd15d9df6fee1e
2018-07-27 21:47:26 +02:00
global:
liblog: add stubs variant Ensure that only the symbols in liblog.map.txt can be used by the platform. Bug: 123349183 Test: build Change-Id: I99ae5d0e8ba8f5061ec20701c941d861c9eb615d
2019-02-08 20:55:36 +01:00
__android_log_bswrite; # apex
__android_log_btwrite; # apex
__android_log_bwrite; # apex
__android_log_close; # apex
__android_log_security; # apex
Rename # vndk tag to # llndk The APIs that are tagged with # vndk are actually for LLNDK libraries. Although LLNDK is part of VNDK, calling those APIs 'vndk' has given users a wrong perception that the APIs don't need to be kept stable because that's the norm for most of the VNDK libraries that are not LLNDK. In order to eliminate the misunderstanding, rename the tag to 'llndk' so that people introducing new such API will realize what they are signing themselves up for. Bug: 143765505 Test: m Merged-In: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6 (cherry picked from commit 0e957b82c8afa24ac10960665316047b970a5b90) Change-Id: Iae2acdf1ff4097a64a5c6280797c66abb1d5a5e6
2019-11-06 04:45:10 +01:00
android_log_reset; # llndk
android_log_parser_reset; # llndk
liblog: Add functions to reset log context Add android_log_parser_reset and android_log_reset to reset reader/writer log context. This allows to generate multiple log messages of the same format without context reallocation. Change-Id: Icb0f15855378aa4e66fc671ffefd15d9df6fee1e
2018-07-27 21:47:26 +02:00
};
Add a version script for liblog for the platform liblog has a version script for the NDK and VNDK, however it doesn't have symbols intended to be used by the platform. This change adds those symbols to the version script and enables it, hiding the rest of the symbols. Test: build Change-Id: I494d048d78bb47d763482eb56a6f79babfe163f4
2019-01-17 20:38:31 +01:00
Fixed a typo in the version name Bug: 149569129 Test: m Change-Id: I7401e8c092d4ee329fb1b5f23b7797f706b58faa
2020-03-03 08:12:09 +01:00
LIBLOG_R { # introduced=30
Add version #29 and #30 to liblog bug: 147759770 test: build Change-Id: I38bcab9bc14088adbdbc3a92620f89a6fe397994
2020-01-15 22:58:13 +01:00
global:
Move SetLogger and SetAborter from libbase to liblog libbase is copied into each APEX module which requires it, meaning that there may be multiple instances of libbase running within a single process with their own copy of libbase's globals. This means that SetLogger() and SetAborter() will only impact logs from the instance of libbase that calls it. This change moves this state to liblog, since it will only ever have one instance in a single process. One major side-effect here is that now both ALOGE style and LOG(...) style logs will be handled through the same logger function. For example, a logger specified through libbase's SetLogger() will now see logs sent to liblog through ALOGE(). This is intended behavior. A second side-effect is that libbase's stderr logger is used for all host logging now. It's simply a better logging default than the fake_log_device logger in liblog currently and makes ALOGE and LOG(...) logs on host follow the same format. Bug: 119867234 Test: libbase and liblog unit tests; logging works Change-Id: Ib52cbfb4e43749e50910ed19a993dffae19ace86
2020-01-08 23:47:42 +01:00
__android_log_call_aborter;
__android_log_default_aborter;
Move minimum log priority from libbase to liblog See the previous commit moving SetLogger and SetAborter to liblog for motivation. This creates more harmony between the two mechanisms in libbase and liblog for checking loggability. Currently: 1) libbase filters all messages based on its minimum log priority. For example, if minimum log priority in libbase remained at its default, but a tag was specifically opted into DEBUG logs via log.tag.<tag>, libbase would not print this log. 2) liblog ignores libbase's minimum log priority. For example if a process called SetMinimumLogPriority(WARNING) but used a library that logged via liblog's ALOGI macro, that log would still be printed even though the process intends on filtering out those INFO messages. With this change: 1) If both a minimum log priority and a priority through log.tag.<tag> are set, then the lower of the two values is used. 2) If only one or the other is set, then that value is used. This fixes the two issues described above. 3) If neither of these values are set, then the default of using INFO is unchanged. Bug: 116329414 Bug: 119867234 Test: libbase and liblog minimum log priority tests Change-Id: Icb49b30b9d93bf797470e23730ae9e537931bb6c
2020-01-17 00:58:02 +01:00
__android_log_get_minimum_priority;
Move SetLogger and SetAborter from libbase to liblog libbase is copied into each APEX module which requires it, meaning that there may be multiple instances of libbase running within a single process with their own copy of libbase's globals. This means that SetLogger() and SetAborter() will only impact logs from the instance of libbase that calls it. This change moves this state to liblog, since it will only ever have one instance in a single process. One major side-effect here is that now both ALOGE style and LOG(...) style logs will be handled through the same logger function. For example, a logger specified through libbase's SetLogger() will now see logs sent to liblog through ALOGE(). This is intended behavior. A second side-effect is that libbase's stderr logger is used for all host logging now. It's simply a better logging default than the fake_log_device logger in liblog currently and makes ALOGE and LOG(...) logs on host follow the same format. Bug: 119867234 Test: libbase and liblog unit tests; logging works Change-Id: Ib52cbfb4e43749e50910ed19a993dffae19ace86
2020-01-08 23:47:42 +01:00
__android_log_logd_logger;
Add version #29 and #30 to liblog bug: 147759770 test: build Change-Id: I38bcab9bc14088adbdbc3a92620f89a6fe397994
2020-01-15 22:58:13 +01:00
__android_log_security_bswrite; # apex
Move SetLogger and SetAborter from libbase to liblog libbase is copied into each APEX module which requires it, meaning that there may be multiple instances of libbase running within a single process with their own copy of libbase's globals. This means that SetLogger() and SetAborter() will only impact logs from the instance of libbase that calls it. This change moves this state to liblog, since it will only ever have one instance in a single process. One major side-effect here is that now both ALOGE style and LOG(...) style logs will be handled through the same logger function. For example, a logger specified through libbase's SetLogger() will now see logs sent to liblog through ALOGE(). This is intended behavior. A second side-effect is that libbase's stderr logger is used for all host logging now. It's simply a better logging default than the fake_log_device logger in liblog currently and makes ALOGE and LOG(...) logs on host follow the same format. Bug: 119867234 Test: libbase and liblog unit tests; logging works Change-Id: Ib52cbfb4e43749e50910ed19a993dffae19ace86
2020-01-08 23:47:42 +01:00
__android_log_set_aborter;
Move default tag from libbase to liblog Bug: 119867234 Test: log tags look right, libbase/liblog unit tests Change-Id: I3670c3fdce3d0238a23a53bba2877ffed1291f9c
2020-01-22 16:48:42 +01:00
__android_log_set_default_tag;
Move SetLogger and SetAborter from libbase to liblog libbase is copied into each APEX module which requires it, meaning that there may be multiple instances of libbase running within a single process with their own copy of libbase's globals. This means that SetLogger() and SetAborter() will only impact logs from the instance of libbase that calls it. This change moves this state to liblog, since it will only ever have one instance in a single process. One major side-effect here is that now both ALOGE style and LOG(...) style logs will be handled through the same logger function. For example, a logger specified through libbase's SetLogger() will now see logs sent to liblog through ALOGE(). This is intended behavior. A second side-effect is that libbase's stderr logger is used for all host logging now. It's simply a better logging default than the fake_log_device logger in liblog currently and makes ALOGE and LOG(...) logs on host follow the same format. Bug: 119867234 Test: libbase and liblog unit tests; logging works Change-Id: Ib52cbfb4e43749e50910ed19a993dffae19ace86
2020-01-08 23:47:42 +01:00
__android_log_set_logger;
Move minimum log priority from libbase to liblog See the previous commit moving SetLogger and SetAborter to liblog for motivation. This creates more harmony between the two mechanisms in libbase and liblog for checking loggability. Currently: 1) libbase filters all messages based on its minimum log priority. For example, if minimum log priority in libbase remained at its default, but a tag was specifically opted into DEBUG logs via log.tag.<tag>, libbase would not print this log. 2) liblog ignores libbase's minimum log priority. For example if a process called SetMinimumLogPriority(WARNING) but used a library that logged via liblog's ALOGI macro, that log would still be printed even though the process intends on filtering out those INFO messages. With this change: 1) If both a minimum log priority and a priority through log.tag.<tag> are set, then the lower of the two values is used. 2) If only one or the other is set, then that value is used. This fixes the two issues described above. 3) If neither of these values are set, then the default of using INFO is unchanged. Bug: 116329414 Bug: 119867234 Test: libbase and liblog minimum log priority tests Change-Id: Icb49b30b9d93bf797470e23730ae9e537931bb6c
2020-01-17 00:58:02 +01:00
__android_log_set_minimum_priority;
Move SetLogger and SetAborter from libbase to liblog libbase is copied into each APEX module which requires it, meaning that there may be multiple instances of libbase running within a single process with their own copy of libbase's globals. This means that SetLogger() and SetAborter() will only impact logs from the instance of libbase that calls it. This change moves this state to liblog, since it will only ever have one instance in a single process. One major side-effect here is that now both ALOGE style and LOG(...) style logs will be handled through the same logger function. For example, a logger specified through libbase's SetLogger() will now see logs sent to liblog through ALOGE(). This is intended behavior. A second side-effect is that libbase's stderr logger is used for all host logging now. It's simply a better logging default than the fake_log_device logger in liblog currently and makes ALOGE and LOG(...) logs on host follow the same format. Bug: 119867234 Test: libbase and liblog unit tests; logging works Change-Id: Ib52cbfb4e43749e50910ed19a993dffae19ace86
2020-01-08 23:47:42 +01:00
__android_log_stderr_logger;
__android_log_write_logger_data;
Add version #29 and #30 to liblog bug: 147759770 test: build Change-Id: I38bcab9bc14088adbdbc3a92620f89a6fe397994
2020-01-15 22:58:13 +01:00
};
Add a version script for liblog for the platform liblog has a version script for the NDK and VNDK, however it doesn't have symbols intended to be used by the platform. This change adds those symbols to the version script and enables it, hiding the rest of the symbols. Test: build Change-Id: I494d048d78bb47d763482eb56a6f79babfe163f4
2019-01-17 20:38:31 +01:00
LIBLOG_PRIVATE {
global:
__android_log_pmsg_file_read;
__android_log_pmsg_file_write;
__android_logger_get_buffer_size;
__android_logger_property_get_bool;
android_openEventTagMap;
android_log_processBinaryLogBuffer;
android_log_processLogBuffer;
android_log_read_next;
android_log_write_list_buffer;
android_lookupEventTagNum;
create_android_log_parser;
};
Reference in a new issue Copy permalink