gecko-dev/memory
Nazım Can Altınova c896734446 Bug 1779257 - Fix the stack walking for linux markers by calling getcontext in a valid stack frame r=mstange
See my comment on here for more context of my investigation:
https://bugzilla.mozilla.org/show_bug.cgi?id=1779257#c9

The saved context is invalid once the function that called `getcontext`
returns. We need to call the `getcontext` while the frame where we called it is
still on the stack. That's why this patch is moving the call to `getcontext` to
parent function by inlining the SyncPopulate content by using a macro instead.
This has to be a macro instead of a function because stack pointer address will
be invalid once the `Registers::SyncPopulate` returns. I tried to change this
method to inline but that didn't help either.

Differential Revision: https://phabricator.services.mozilla.com/D170133
2023-02-22 19:57:08 +00:00
..
build Bug 1814808 - Move chunk releasing out of the arena lock's critical section r=glandium 2023-02-17 04:17:24 +00:00
gtest Bug 1798711 - Remove duplication of DisableCrashReporter on gtest r=ahal 2022-11-30 14:41:42 +00:00
mozalloc Backed out changeset e59efc28ac89 (bug 1802675) for causing win10 2004 failures CLOSED TREE 2022-12-02 00:11:36 -05:00
mozjemalloc_info Bug 1743713 - Make --enable-project=memory work again r=glandium 2021-12-07 22:27:20 +00:00
replace Bug 1779257 - Fix the stack walking for linux markers by calling getcontext in a valid stack frame r=mstange 2023-02-22 19:57:08 +00:00
volatile Bug 1207753 - Add MOZ_UNANNOTATED to all Mutexes/Monitors r=nika,kershaw 2022-03-16 18:47:08 +00:00
app.mozbuild Bug 1706774: Adds required sources for the "memory" application r=firefox-build-system-reviewers,glandium 2021-05-18 15:00:39 +00:00
moz.build Bug 1670188 - pt 2. Add a tool that prints the run lengths for size classes r=glandium 2020-11-20 03:33:57 +00:00
moz.configure Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00