зеркало из https://github.com/mozilla/gecko-dev.git
ec7f538e0c
In the case of FramePointerStackwalk, the caller gives a pointer to the top-most frame to walk from. There isn't really a reason to give a number of frames to skip, as the right frame pointer could be given in the first place if that was really necessary. And in practice, it's hasn't been used so far. In the case of MozStackWalkThread, the caller presumably doesn't know what the thread the stack is being walked for is doing, and it would be a guesswork to pass a valid number of frames to skip. In practice, it's also not used. The aSkipFrames is already a footgun on MozStackWalk (and we're going to change that in bug 1515229), we don't need to keep a footgun on these other stack walking methods. Differential Revision: https://phabricator.services.mozilla.com/D108563 |
||
|---|---|---|
| .. | ||
| android | ||
| baseprofiler | ||
| build | ||
| dllservices | ||
| linker | ||
| misc | ||
| static | ||
| tests | ||
| moz.build | ||