History log of /external/google-breakpad/src/google_breakpad/common/minidump_cpu_amd64.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6162aed3c3fcfc53373c963ac375d39a5dfa5a25 06-Mar-2013 ted.mielczarek@gmail.com <ted.mielczarek@gmail.com@4c0a9323-5329-0410-9bdc-e9ce6186880e> Use stdint types everywhere
R=mark at https://breakpad.appspot.com/535002/

git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1121 4c0a9323-5329-0410-9bdc-e9ce6186880e
/external/google-breakpad/src/google_breakpad/common/minidump_cpu_amd64.h
1a1890a52aaf8bfbea34a8d918423e6c81f3ea80 31-Aug-2011 ted.mielczarek <ted.mielczarek@4c0a9323-5329-0410-9bdc-e9ce6186880e> 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
/external/google-breakpad/src/google_breakpad/common/minidump_cpu_amd64.h
a194d6f1acbcd3f941b228901a02a0708f1c2ad5 17-Mar-2008 nealsid <nealsid@4c0a9323-5329-0410-9bdc-e9ce6186880e> Issue 245: refactoring minidump_format.h into architecture & platform specific files

git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@249 4c0a9323-5329-0410-9bdc-e9ce6186880e
/external/google-breakpad/src/google_breakpad/common/minidump_cpu_amd64.h