From e780ef28b84c03b7b234de9d3fb843d90ab0e21d Mon Sep 17 00:00:00 2001 From: TCMalloc Team Date: Fri, 17 Jan 2025 09:25:14 -0800 Subject: [PATCH] Adding a bit of guidance about which crash stacks to focus on when debugging the mismatched sized delete diagnostic. PiperOrigin-RevId: 716695791 Change-Id: Ib7f65f84b64dca51896efef8ad1d8d32062452d4 --- docs/mismatched-sized-delete.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/mismatched-sized-delete.md b/docs/mismatched-sized-delete.md index 6a6ee4491..299eaff8f 100644 --- a/docs/mismatched-sized-delete.md +++ b/docs/mismatched-sized-delete.md @@ -40,6 +40,11 @@ Mismatched-size-class (https://github.com/google/tcmalloc/tree/master/docs/misma ## TCMalloc is buggy? +TIP: Memory safety bugs can have a delayed effect. The checks described above, +and other related crashes, often occur in a different call stack than the one +that caused the bug. Before scrutinizing the call stack attached to this crash, +start by looking for related crashes of the same process. + It is not a bug in TCMalloc. It is detecting an erroneous argument provided to `::operator delete`.