2010-03-16 17:28:32 +01:00
|
|
|
// -*- mode: c++ -*-
|
|
|
|
|
|
2010-02-09 18:08:56 +01:00
|
|
|
// Copyright (c) 2010 Google Inc.
|
2006-10-20 03:46:38 +02:00
|
|
|
// All rights reserved.
|
|
|
|
|
//
|
|
|
|
|
// Redistribution and use in source and binary forms, with or without
|
|
|
|
|
// modification, are permitted provided that the following conditions are
|
|
|
|
|
// met:
|
|
|
|
|
//
|
|
|
|
|
// * Redistributions of source code must retain the above copyright
|
|
|
|
|
// notice, this list of conditions and the following disclaimer.
|
|
|
|
|
// * Redistributions in binary form must reproduce the above
|
|
|
|
|
// copyright notice, this list of conditions and the following disclaimer
|
|
|
|
|
// in the documentation and/or other materials provided with the
|
|
|
|
|
// distribution.
|
|
|
|
|
// * Neither the name of Google Inc. nor the names of its
|
|
|
|
|
// contributors may be used to endorse or promote products derived from
|
|
|
|
|
// this software without specific prior written permission.
|
|
|
|
|
//
|
|
|
|
|
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
|
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
|
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
|
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
|
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
|
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
|
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
|
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
|
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
|
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
|
|
|
|
|
// stack_frame_cpu.h: CPU-specific StackFrame extensions.
|
|
|
|
|
//
|
|
|
|
|
// These types extend the StackFrame structure to carry CPU-specific register
|
|
|
|
|
// state. They are defined in this header instead of stack_frame.h to
|
|
|
|
|
// avoid the need to include minidump_format.h when only the generic
|
|
|
|
|
// StackFrame type is needed.
|
|
|
|
|
//
|
|
|
|
|
// Author: Mark Mentovai
|
|
|
|
|
|
2007-02-14 20:51:05 +01:00
|
|
|
#ifndef GOOGLE_BREAKPAD_PROCESSOR_STACK_FRAME_CPU_H__
|
|
|
|
|
#define GOOGLE_BREAKPAD_PROCESSOR_STACK_FRAME_CPU_H__
|
2006-10-20 03:46:38 +02:00
|
|
|
|
2007-02-14 20:51:05 +01:00
|
|
|
#include "google_breakpad/common/minidump_format.h"
|
|
|
|
|
#include "google_breakpad/processor/stack_frame.h"
|
2006-10-20 03:46:38 +02:00
|
|
|
|
2007-02-14 20:51:05 +01:00
|
|
|
namespace google_breakpad {
|
2006-10-20 03:46:38 +02:00
|
|
|
|
2010-01-14 20:17:36 +01:00
|
|
|
struct WindowsFrameInfo;
|
2012-03-30 07:01:50 +02:00
|
|
|
class CFIFrameInfo;
|
2010-01-14 20:17:36 +01:00
|
|
|
|
2006-10-20 03:46:38 +02:00
|
|
|
struct StackFrameX86 : public StackFrame {
|
2010-03-16 17:28:32 +01:00
|
|
|
// ContextValidity has one entry for each relevant hardware pointer
|
|
|
|
|
// register (%eip and %esp) and one entry for each general-purpose
|
|
|
|
|
// register. It's worthwhile having validity flags for caller-saves
|
|
|
|
|
// registers: they are valid in the youngest frame, and such a frame
|
|
|
|
|
// might save a callee-saves register in a caller-saves register, but
|
|
|
|
|
// SimpleCFIWalker won't touch registers unless they're marked as valid.
|
2006-10-20 03:46:38 +02:00
|
|
|
enum ContextValidity {
|
|
|
|
|
CONTEXT_VALID_NONE = 0,
|
|
|
|
|
CONTEXT_VALID_EIP = 1 << 0,
|
|
|
|
|
CONTEXT_VALID_ESP = 1 << 1,
|
|
|
|
|
CONTEXT_VALID_EBP = 1 << 2,
|
2010-03-16 17:28:32 +01:00
|
|
|
CONTEXT_VALID_EAX = 1 << 3,
|
|
|
|
|
CONTEXT_VALID_EBX = 1 << 4,
|
|
|
|
|
CONTEXT_VALID_ECX = 1 << 5,
|
|
|
|
|
CONTEXT_VALID_EDX = 1 << 6,
|
|
|
|
|
CONTEXT_VALID_ESI = 1 << 7,
|
|
|
|
|
CONTEXT_VALID_EDI = 1 << 8,
|
2006-10-20 03:46:38 +02:00
|
|
|
CONTEXT_VALID_ALL = -1
|
|
|
|
|
};
|
|
|
|
|
|
2012-10-10 23:41:52 +02:00
|
|
|
StackFrameX86()
|
2009-10-08 16:21:50 +02:00
|
|
|
: context(),
|
|
|
|
|
context_validity(CONTEXT_VALID_NONE),
|
2010-03-16 17:28:32 +01:00
|
|
|
windows_frame_info(NULL),
|
|
|
|
|
cfi_frame_info(NULL) {}
|
2010-01-14 20:17:36 +01:00
|
|
|
~StackFrameX86();
|
2006-10-20 03:46:38 +02:00
|
|
|
|
|
|
|
|
// Register state. This is only fully valid for the topmost frame in a
|
|
|
|
|
// stack. In other frames, the values of nonvolatile registers may be
|
|
|
|
|
// present, given sufficient debugging information. Refer to
|
|
|
|
|
// context_validity.
|
|
|
|
|
MDRawContextX86 context;
|
|
|
|
|
|
|
|
|
|
// context_validity is actually ContextValidity, but int is used because
|
|
|
|
|
// the OR operator doesn't work well with enumerated types. This indicates
|
|
|
|
|
// which fields in context are valid.
|
|
|
|
|
int context_validity;
|
2010-01-14 20:17:36 +01:00
|
|
|
|
2010-03-16 17:28:32 +01:00
|
|
|
// Any stack walking information we found describing this.instruction.
|
|
|
|
|
// These may be NULL if there is no such information for that address.
|
2010-01-14 20:17:36 +01:00
|
|
|
WindowsFrameInfo *windows_frame_info;
|
2010-03-16 17:28:32 +01:00
|
|
|
CFIFrameInfo *cfi_frame_info;
|
2006-10-20 03:46:38 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct StackFramePPC : public StackFrame {
|
|
|
|
|
// ContextValidity should eventually contain entries for the validity of
|
|
|
|
|
// other nonvolatile (callee-save) registers as in
|
|
|
|
|
// StackFrameX86::ContextValidity, but the ppc stackwalker doesn't currently
|
|
|
|
|
// locate registers other than the ones listed here.
|
|
|
|
|
enum ContextValidity {
|
|
|
|
|
CONTEXT_VALID_NONE = 0,
|
|
|
|
|
CONTEXT_VALID_SRR0 = 1 << 0,
|
|
|
|
|
CONTEXT_VALID_GPR1 = 1 << 1,
|
|
|
|
|
CONTEXT_VALID_ALL = -1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
StackFramePPC() : context(), context_validity(CONTEXT_VALID_NONE) {}
|
|
|
|
|
|
|
|
|
|
// Register state. This is only fully valid for the topmost frame in a
|
|
|
|
|
// stack. In other frames, the values of nonvolatile registers may be
|
|
|
|
|
// present, given sufficient debugging information. Refer to
|
|
|
|
|
// context_validity.
|
|
|
|
|
MDRawContextPPC context;
|
|
|
|
|
|
|
|
|
|
// context_validity is actually ContextValidity, but int is used because
|
|
|
|
|
// the OR operator doesn't work well with enumerated types. This indicates
|
2007-10-31 20:20:31 +01:00
|
|
|
// which fields in context are valid.
|
|
|
|
|
int context_validity;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct StackFrameAMD64 : public StackFrame {
|
2010-03-16 17:49:53 +01:00
|
|
|
// ContextValidity has one entry for each register that we might be able
|
|
|
|
|
// to recover.
|
2007-10-31 20:20:31 +01:00
|
|
|
enum ContextValidity {
|
2010-03-16 17:49:53 +01:00
|
|
|
CONTEXT_VALID_NONE = 0,
|
|
|
|
|
CONTEXT_VALID_RAX = 1 << 0,
|
|
|
|
|
CONTEXT_VALID_RDX = 1 << 1,
|
|
|
|
|
CONTEXT_VALID_RCX = 1 << 2,
|
|
|
|
|
CONTEXT_VALID_RBX = 1 << 3,
|
|
|
|
|
CONTEXT_VALID_RSI = 1 << 4,
|
|
|
|
|
CONTEXT_VALID_RDI = 1 << 5,
|
|
|
|
|
CONTEXT_VALID_RBP = 1 << 6,
|
|
|
|
|
CONTEXT_VALID_RSP = 1 << 7,
|
|
|
|
|
CONTEXT_VALID_R8 = 1 << 8,
|
|
|
|
|
CONTEXT_VALID_R9 = 1 << 9,
|
|
|
|
|
CONTEXT_VALID_R10 = 1 << 10,
|
|
|
|
|
CONTEXT_VALID_R11 = 1 << 11,
|
|
|
|
|
CONTEXT_VALID_R12 = 1 << 12,
|
|
|
|
|
CONTEXT_VALID_R13 = 1 << 13,
|
|
|
|
|
CONTEXT_VALID_R14 = 1 << 14,
|
|
|
|
|
CONTEXT_VALID_R15 = 1 << 15,
|
|
|
|
|
CONTEXT_VALID_RIP = 1 << 16,
|
2007-10-31 20:20:31 +01:00
|
|
|
CONTEXT_VALID_ALL = -1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
StackFrameAMD64() : context(), context_validity(CONTEXT_VALID_NONE) {}
|
|
|
|
|
|
2010-03-16 17:49:53 +01:00
|
|
|
// Register state. This is only fully valid for the topmost frame in a
|
|
|
|
|
// stack. In other frames, which registers are present depends on what
|
|
|
|
|
// debugging information we had available. Refer to context_validity.
|
2007-10-31 20:20:31 +01:00
|
|
|
MDRawContextAMD64 context;
|
|
|
|
|
|
2010-03-16 17:49:53 +01:00
|
|
|
// For each register in context whose value has been recovered, we set
|
|
|
|
|
// the corresponding CONTEXT_VALID_ bit in context_validity.
|
|
|
|
|
//
|
|
|
|
|
// context_validity's type should actually be ContextValidity, but
|
|
|
|
|
// we use int instead because the bitwise inclusive or operator
|
|
|
|
|
// yields an int when applied to enum values, and C++ doesn't
|
|
|
|
|
// silently convert from ints to enums.
|
2006-10-20 03:46:38 +02:00
|
|
|
int context_validity;
|
|
|
|
|
};
|
|
|
|
|
|
2007-09-26 20:28:05 +02:00
|
|
|
struct StackFrameSPARC : public StackFrame {
|
|
|
|
|
// to be confirmed
|
|
|
|
|
enum ContextValidity {
|
|
|
|
|
CONTEXT_VALID_NONE = 0,
|
2008-03-18 17:10:10 +01:00
|
|
|
CONTEXT_VALID_PC = 1 << 0,
|
|
|
|
|
CONTEXT_VALID_SP = 1 << 1,
|
|
|
|
|
CONTEXT_VALID_FP = 1 << 2,
|
2007-09-26 20:28:05 +02:00
|
|
|
CONTEXT_VALID_ALL = -1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
StackFrameSPARC() : context(), context_validity(CONTEXT_VALID_NONE) {}
|
|
|
|
|
|
|
|
|
|
// Register state. This is only fully valid for the topmost frame in a
|
|
|
|
|
// stack. In other frames, the values of nonvolatile registers may be
|
|
|
|
|
// present, given sufficient debugging information. Refer to
|
|
|
|
|
// context_validity.
|
|
|
|
|
MDRawContextSPARC context;
|
|
|
|
|
|
|
|
|
|
// context_validity is actually ContextValidity, but int is used because
|
|
|
|
|
// the OR operator doesn't work well with enumerated types. This indicates
|
|
|
|
|
// which fields in context are valid.
|
|
|
|
|
int context_validity;
|
|
|
|
|
};
|
|
|
|
|
|
2009-12-19 22:43:53 +01:00
|
|
|
struct StackFrameARM : public StackFrame {
|
Breakpad: Support DWARF CFI-driven stack walking on ARM.
This patch allows the Breakpad minidump processor to use data from
STACK CFI records to generate stack traces for the ARM processor.
In the symbol dumper, we need a table mapping DWARF CFI register
numbers to their names: STACK CFI records refer to registers by name.
In the processor, we expand StackwalkerARM::GetCallerFrame to see if
there are STACK CFI records covering the callee, and then use those to
recover the caller's register values.
There's no good reason the ARM walker couldn't use the SimpleCFIWalker
interface declared in cfi_frame_info.h. Unfortunately, that interface
assumes that one can map register names to member pointers of the raw
context type, while MDRawContextARM uses an array to hold the
registers' values: C++ pointer-to-member types can't refer to elements
of member arrays. So we have to write out SimpleCFIWalker::FindCallerRegisters
in StackwalkerARM::GetCallerFrame.
We define enum MDARMRegisterNumbers in minidump_cpu_arm.h, for
convenience in referring to certain ARM registers with dedicated
purposes, like the stack pointer and the PC.
We define validity flags in StackFrameARM for all the registers, since
CFI could theoretically recover any of them. In the same vein, we
expand minidump_stackwalk.cc to print the values of all valid
callee-saves registers in the context --- and use the proper names for
special-purpose registers.
We provide unit tests that give full code and branch coverage (with
minor exceptions). We add a testing interface to StackwalkerARM that
allows us to create context frames that lack some register values.
a=jimblandy, r=mmentovai
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@553 4c0a9323-5329-0410-9bdc-e9ce6186880e
2010-03-16 17:46:22 +01:00
|
|
|
// A flag for each register we might know.
|
2009-12-19 22:43:53 +01:00
|
|
|
enum ContextValidity {
|
|
|
|
|
CONTEXT_VALID_NONE = 0,
|
Breakpad: Support DWARF CFI-driven stack walking on ARM.
This patch allows the Breakpad minidump processor to use data from
STACK CFI records to generate stack traces for the ARM processor.
In the symbol dumper, we need a table mapping DWARF CFI register
numbers to their names: STACK CFI records refer to registers by name.
In the processor, we expand StackwalkerARM::GetCallerFrame to see if
there are STACK CFI records covering the callee, and then use those to
recover the caller's register values.
There's no good reason the ARM walker couldn't use the SimpleCFIWalker
interface declared in cfi_frame_info.h. Unfortunately, that interface
assumes that one can map register names to member pointers of the raw
context type, while MDRawContextARM uses an array to hold the
registers' values: C++ pointer-to-member types can't refer to elements
of member arrays. So we have to write out SimpleCFIWalker::FindCallerRegisters
in StackwalkerARM::GetCallerFrame.
We define enum MDARMRegisterNumbers in minidump_cpu_arm.h, for
convenience in referring to certain ARM registers with dedicated
purposes, like the stack pointer and the PC.
We define validity flags in StackFrameARM for all the registers, since
CFI could theoretically recover any of them. In the same vein, we
expand minidump_stackwalk.cc to print the values of all valid
callee-saves registers in the context --- and use the proper names for
special-purpose registers.
We provide unit tests that give full code and branch coverage (with
minor exceptions). We add a testing interface to StackwalkerARM that
allows us to create context frames that lack some register values.
a=jimblandy, r=mmentovai
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@553 4c0a9323-5329-0410-9bdc-e9ce6186880e
2010-03-16 17:46:22 +01:00
|
|
|
CONTEXT_VALID_R0 = 1 << 0,
|
|
|
|
|
CONTEXT_VALID_R1 = 1 << 1,
|
|
|
|
|
CONTEXT_VALID_R2 = 1 << 2,
|
|
|
|
|
CONTEXT_VALID_R3 = 1 << 3,
|
|
|
|
|
CONTEXT_VALID_R4 = 1 << 4,
|
|
|
|
|
CONTEXT_VALID_R5 = 1 << 5,
|
|
|
|
|
CONTEXT_VALID_R6 = 1 << 6,
|
|
|
|
|
CONTEXT_VALID_R7 = 1 << 7,
|
|
|
|
|
CONTEXT_VALID_R8 = 1 << 8,
|
|
|
|
|
CONTEXT_VALID_R9 = 1 << 9,
|
|
|
|
|
CONTEXT_VALID_R10 = 1 << 10,
|
|
|
|
|
CONTEXT_VALID_R11 = 1 << 11,
|
|
|
|
|
CONTEXT_VALID_R12 = 1 << 12,
|
|
|
|
|
CONTEXT_VALID_R13 = 1 << 13,
|
|
|
|
|
CONTEXT_VALID_R14 = 1 << 14,
|
|
|
|
|
CONTEXT_VALID_R15 = 1 << 15,
|
|
|
|
|
CONTEXT_VALID_ALL = ~CONTEXT_VALID_NONE,
|
|
|
|
|
|
|
|
|
|
// Aliases for registers with dedicated or conventional roles.
|
|
|
|
|
CONTEXT_VALID_FP = CONTEXT_VALID_R11,
|
|
|
|
|
CONTEXT_VALID_SP = CONTEXT_VALID_R13,
|
|
|
|
|
CONTEXT_VALID_LR = CONTEXT_VALID_R14,
|
|
|
|
|
CONTEXT_VALID_PC = CONTEXT_VALID_R15
|
2009-12-19 22:43:53 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
StackFrameARM() : context(), context_validity(CONTEXT_VALID_NONE) {}
|
|
|
|
|
|
Breakpad: Support DWARF CFI-driven stack walking on ARM.
This patch allows the Breakpad minidump processor to use data from
STACK CFI records to generate stack traces for the ARM processor.
In the symbol dumper, we need a table mapping DWARF CFI register
numbers to their names: STACK CFI records refer to registers by name.
In the processor, we expand StackwalkerARM::GetCallerFrame to see if
there are STACK CFI records covering the callee, and then use those to
recover the caller's register values.
There's no good reason the ARM walker couldn't use the SimpleCFIWalker
interface declared in cfi_frame_info.h. Unfortunately, that interface
assumes that one can map register names to member pointers of the raw
context type, while MDRawContextARM uses an array to hold the
registers' values: C++ pointer-to-member types can't refer to elements
of member arrays. So we have to write out SimpleCFIWalker::FindCallerRegisters
in StackwalkerARM::GetCallerFrame.
We define enum MDARMRegisterNumbers in minidump_cpu_arm.h, for
convenience in referring to certain ARM registers with dedicated
purposes, like the stack pointer and the PC.
We define validity flags in StackFrameARM for all the registers, since
CFI could theoretically recover any of them. In the same vein, we
expand minidump_stackwalk.cc to print the values of all valid
callee-saves registers in the context --- and use the proper names for
special-purpose registers.
We provide unit tests that give full code and branch coverage (with
minor exceptions). We add a testing interface to StackwalkerARM that
allows us to create context frames that lack some register values.
a=jimblandy, r=mmentovai
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@553 4c0a9323-5329-0410-9bdc-e9ce6186880e
2010-03-16 17:46:22 +01:00
|
|
|
// Return the ContextValidity flag for register rN.
|
|
|
|
|
static ContextValidity RegisterValidFlag(int n) {
|
|
|
|
|
return ContextValidity(1 << n);
|
2012-10-10 23:41:52 +02:00
|
|
|
}
|
Breakpad: Support DWARF CFI-driven stack walking on ARM.
This patch allows the Breakpad minidump processor to use data from
STACK CFI records to generate stack traces for the ARM processor.
In the symbol dumper, we need a table mapping DWARF CFI register
numbers to their names: STACK CFI records refer to registers by name.
In the processor, we expand StackwalkerARM::GetCallerFrame to see if
there are STACK CFI records covering the callee, and then use those to
recover the caller's register values.
There's no good reason the ARM walker couldn't use the SimpleCFIWalker
interface declared in cfi_frame_info.h. Unfortunately, that interface
assumes that one can map register names to member pointers of the raw
context type, while MDRawContextARM uses an array to hold the
registers' values: C++ pointer-to-member types can't refer to elements
of member arrays. So we have to write out SimpleCFIWalker::FindCallerRegisters
in StackwalkerARM::GetCallerFrame.
We define enum MDARMRegisterNumbers in minidump_cpu_arm.h, for
convenience in referring to certain ARM registers with dedicated
purposes, like the stack pointer and the PC.
We define validity flags in StackFrameARM for all the registers, since
CFI could theoretically recover any of them. In the same vein, we
expand minidump_stackwalk.cc to print the values of all valid
callee-saves registers in the context --- and use the proper names for
special-purpose registers.
We provide unit tests that give full code and branch coverage (with
minor exceptions). We add a testing interface to StackwalkerARM that
allows us to create context frames that lack some register values.
a=jimblandy, r=mmentovai
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@553 4c0a9323-5329-0410-9bdc-e9ce6186880e
2010-03-16 17:46:22 +01:00
|
|
|
|
2009-12-19 22:43:53 +01:00
|
|
|
// Register state. This is only fully valid for the topmost frame in a
|
|
|
|
|
// stack. In other frames, the values of nonvolatile registers may be
|
|
|
|
|
// present, given sufficient debugging information. Refer to
|
|
|
|
|
// context_validity.
|
|
|
|
|
MDRawContextARM context;
|
|
|
|
|
|
Breakpad: Support DWARF CFI-driven stack walking on ARM.
This patch allows the Breakpad minidump processor to use data from
STACK CFI records to generate stack traces for the ARM processor.
In the symbol dumper, we need a table mapping DWARF CFI register
numbers to their names: STACK CFI records refer to registers by name.
In the processor, we expand StackwalkerARM::GetCallerFrame to see if
there are STACK CFI records covering the callee, and then use those to
recover the caller's register values.
There's no good reason the ARM walker couldn't use the SimpleCFIWalker
interface declared in cfi_frame_info.h. Unfortunately, that interface
assumes that one can map register names to member pointers of the raw
context type, while MDRawContextARM uses an array to hold the
registers' values: C++ pointer-to-member types can't refer to elements
of member arrays. So we have to write out SimpleCFIWalker::FindCallerRegisters
in StackwalkerARM::GetCallerFrame.
We define enum MDARMRegisterNumbers in minidump_cpu_arm.h, for
convenience in referring to certain ARM registers with dedicated
purposes, like the stack pointer and the PC.
We define validity flags in StackFrameARM for all the registers, since
CFI could theoretically recover any of them. In the same vein, we
expand minidump_stackwalk.cc to print the values of all valid
callee-saves registers in the context --- and use the proper names for
special-purpose registers.
We provide unit tests that give full code and branch coverage (with
minor exceptions). We add a testing interface to StackwalkerARM that
allows us to create context frames that lack some register values.
a=jimblandy, r=mmentovai
git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@553 4c0a9323-5329-0410-9bdc-e9ce6186880e
2010-03-16 17:46:22 +01:00
|
|
|
// For each register in context whose value has been recovered, we set
|
|
|
|
|
// the corresponding CONTEXT_VALID_ bit in context_validity.
|
|
|
|
|
//
|
|
|
|
|
// context_validity's type should actually be ContextValidity, but
|
|
|
|
|
// we use int instead because the bitwise inclusive or operator
|
|
|
|
|
// yields an int when applied to enum values, and C++ doesn't
|
|
|
|
|
// silently convert from ints to enums.
|
2009-12-19 22:43:53 +01:00
|
|
|
int context_validity;
|
|
|
|
|
};
|
|
|
|
|
|
2007-02-14 20:51:05 +01:00
|
|
|
} // namespace google_breakpad
|
2006-10-20 03:46:38 +02:00
|
|
|
|
2007-02-14 20:51:05 +01:00
|
|
|
#endif // GOOGLE_BREAKPAD_PROCESSOR_STACK_FRAME_CPU_H__
|