98d6242dc7
Some testing environments can have a test that is sending many thousands of messages to the log. When this type of process crashes all of these log messages are captured and can cause OOM errors while creating the tombstone. Added a test to verify the log messages are truncated. Leaving this test disabled for now since it is inherently flaky due to having to assume that 500 messages are in the log. Added a test for a newline in a log message since it's somewhat related to this change. NOTE: The total number of messages is capped at 500, but if a message contains multiple newlines, the total messages will exceed 500. Counting messages this way seems to be in the spirit of the cap, that a process logging a large message with multiple newlines does not completely fill the tombstone log data. Bug: 269182937 Bug: 282661754 Test: All unit tests pass. Test: The disabled max_log_messages test passes. Change-Id: If18e62b29f899c2c4670101b402e37762bffbec6 |
||
|---|---|---|
| .. | ||
| include/libdebuggerd | ||
| test | ||
| backtrace.cpp | ||
| gwp_asan.cpp | ||
| open_files_list.cpp | ||
| scudo.cpp | ||
| tombstone.cpp | ||
| tombstone_proto.cpp | ||
| tombstone_proto_to_text.cpp | ||
| utility.cpp | ||