Show the number of VMAs in the tombstone.
Tombstones (especially ones with lots of VMAs) are regularly truncated.
We can at least show the number of VMAs, though, for anyone interested
in knowing whether they got close to the default 64Ki limit.
Bug: http://b/66911122
Bug: 64709603 (presubmit balking at the line above)
Test: ran crasher, examined tombstone
(cherry picked from commit 868d39a82f
)
Change-Id: I286db66f28f132307d573dbe5164efc969dc6ddc
This commit is contained in:
parent
5dec8e22c3
commit
bab3354ede
|
@ -415,15 +415,17 @@ static void dump_all_maps(Backtrace* backtrace, BacktraceMap* map, log_t* log, p
|
|||
}
|
||||
|
||||
ScopedBacktraceMapIteratorLock lock(map);
|
||||
_LOG(log, logtype::MAPS, "\n");
|
||||
if (!print_fault_address_marker) {
|
||||
_LOG(log, logtype::MAPS, "memory map:\n");
|
||||
} else {
|
||||
_LOG(log, logtype::MAPS, "memory map: (fault address prefixed with --->)\n");
|
||||
_LOG(log, logtype::MAPS,
|
||||
"\n"
|
||||
"memory map (%zu entries):\n",
|
||||
map->size());
|
||||
if (print_fault_address_marker) {
|
||||
if (map->begin() != map->end() && addr < map->begin()->start) {
|
||||
_LOG(log, logtype::MAPS, "--->Fault address falls at %s before any mapped regions\n",
|
||||
get_addr_string(addr).c_str());
|
||||
print_fault_address_marker = false;
|
||||
} else {
|
||||
_LOG(log, logtype::MAPS, "(fault address prefixed with --->)\n");
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
@ -89,6 +89,8 @@ public:
|
|||
const_iterator begin() const { return maps_.begin(); }
|
||||
const_iterator end() const { return maps_.end(); }
|
||||
|
||||
size_t size() const { return maps_.size(); }
|
||||
|
||||
virtual bool Build();
|
||||
|
||||
static inline bool IsValid(const backtrace_map_t& map) {
|
||||
|
|
Loading…
Reference in New Issue