mirror of
https://git.suyu.dev/suyu/breakpad.git
synced 2025-12-26 01:05:07 +01:00
Use general instruction/stack pointer convenience method instead of manually
finding the instruction/stack pointer for exploitability rating. There was already a method that found the instruction pointer, so the files for exploitability ratings had repeated code. Also a method for finding the stack pointer is implemented in this CL. R=ivanpe@chromium.org Review URL: https://codereview.chromium.org/1210943005 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1468 4c0a9323-5329-0410-9bdc-e9ce6186880e
This commit is contained in:
parent
12213a5e15
commit
e2eb4505d0
7 changed files with 74 additions and 33 deletions
|
|
@ -67,6 +67,10 @@ class DumpContext : public DumpObject {
|
|||
// MDRawContext, since it varies per-CPU architecture.
|
||||
bool GetInstructionPointer(uint64_t* ip) const;
|
||||
|
||||
// Similar to the GetInstructionPointer method, this method gets the stack
|
||||
// pointer for all CPU architectures.
|
||||
bool GetStackPointer(uint64_t* sp) const;
|
||||
|
||||
// Print a human-readable representation of the object to stdout.
|
||||
void Print();
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue