aboutsummaryrefslogtreecommitdiff
path: root/src/third_party/libdisasm
diff options
context:
space:
mode:
authorted.mielczarek <ted.mielczarek@4c0a9323-5329-0410-9bdc-e9ce6186880e>2011-08-30 22:22:08 +0000
committerted.mielczarek <ted.mielczarek@4c0a9323-5329-0410-9bdc-e9ce6186880e>2011-08-30 22:22:08 +0000
commit1a1890a52aaf8bfbea34a8d918423e6c81f3ea80 (patch)
tree24e84b122a562af38ebb1ce28ed0d71046bc7439 /src/third_party/libdisasm
parentissue 243 - Linux dumper should use build id produced by ld --build-id if ava... (diff)
downloadbreakpad-1a1890a52aaf8bfbea34a8d918423e6c81f3ea80.tar.xz
Adjust MD_CONTEXT_CPU_MASK to reflect reality, fix some code so it can handle dumps using the old value for MD_CONTEXT_ARM
The value of MD_CONTEXT_CPU_MASK in use assumes that only the lower 6 bits are used for flags, and the upper 26 bits are for the CPU type. However, as of Windows 7 SP1, the 7th bit is being used as a flag (per http://msdn.microsoft.com/en-us/library/hh134238%28v=vs.85%29.aspx and the Windows SDK headers). Adjusting MD_CONTEXT_CPU_MASK works, but unfortunately that masks off the existing value of MD_CONTEXT_ARM. This patch also changes the value of MD_CONTEXT_ARM and adjusts the minidump context reading machinery to gracefully handle minidumps with the old value. R=mark at http://breakpad.appspot.com/302001 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@831 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/third_party/libdisasm')
0 files changed, 0 insertions, 0 deletions