)]}' { "log": [ { "commit": "3f5c13e7e8f8755dd3fecd8388bbcb840fe3bc06", "tree": "cecc1351b34cdedb3026c2bfdef8874b1474456f", "parents": [ "af196c74f021253533957d38dad876044c5d35c9" ], "author": { "name": "mmandlis@chromium.org", "email": "mmandlis@chromium.org", "time": "Wed Aug 26 16:18:52 2015" }, "committer": { "name": "mmandlis@chromium.org", "email": "mmandlis@chromium.org", "time": "Wed Aug 26 16:18:52 2015" }, "message": "The \"CPU architecture\" field is being filled from the wrong part of\nthe microdump. The microdump OS/arch line looks like:\nO A arm 04 armv7l 3.4.0-perf-g4d6e88e #1 SMP PREEMPT Mon Mar 30 19:09:30 2015\nand currently the field that says \"armv7l\" or \"aarch64\" is being used\nto fill in the CPU arch field in crash. The problem is that on a\n64-bit device this field *always* says \"aarch64\" even when running in\na 32-bit process, and so currently the crash reports for aarch64 are\na mix of 32-bit and 64-bit crashes. We should be using the first field\ninstead, which just says \"arm\" or \"arm64\" and reflects the actual\nversion of webview (32-bit or 64-bit) which is running.\n\nBUG\u003d\nR\u003dprimiano@chromium.org\n\nReview URL: https://codereview.chromium.org/1306983003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1498 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "af196c74f021253533957d38dad876044c5d35c9", "tree": "a5f48cb623a179c17d54f5005f9ab64c23388fca", "parents": [ "c938b7b1c4abdd5f2a5099c61f21a55583ed4fa3" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Fri Aug 21 16:22:19 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Fri Aug 21 16:22:19 2015" }, "message": "Add check for Linux minidump ending on bad write for exploitability rating.\n\nIf a crash occurred as a result to a write to unwritable memory, it is reason\nto suggest exploitability. The processor checks for a bad write by\ndisassembling the command that caused the crash by piping the raw bytes near\nthe instruction pointer through objdump. This allows the processor to see if\nthe instruction that caused the crash is a write to memory and where the\ntarget of the address is located.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1273823004\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1497 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "c938b7b1c4abdd5f2a5099c61f21a55583ed4fa3", "tree": "90e4c82c07e818b5cf874541ed5c79c8891859b4", "parents": [ "e100989d3776aa1a6bfa9453edca227a679e3a0c" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 20 15:09:16 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 20 15:09:16 2015" }, "message": "Don\u0027t use strtok_s for mingw builds\n\nR\u003divanpe at https://codereview.chromium.org/1292503005/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1496 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "e100989d3776aa1a6bfa9453edca227a679e3a0c", "tree": "c6671a80f018a853391a9f16966b85c1dc5b513b", "parents": [ "0ad58e6f57ada0f1a9f1b640b5c590dec3a97d87" ], "author": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Thu Aug 20 14:30:38 2015" }, "committer": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Thu Aug 20 14:30:38 2015" }, "message": "Add user_regs_struct and user_fpsimd_struct for aarch64 on Android.\n\nAndroid\u0027s sys/user.h is missing user_regs_struct and user_fpsimd_struct.\nAdd them to the Android specific user.h used by breakpad to workaround\nAndroid / glibc compatibility issues.\n\nA bug has been filed on the Android NDK team to add the missing structures to\nthe NDK, at which point this hack can be removed.\n\nAlso remove the mxcsr_mask hack on x64, which is no longer required since\nwe have moved to the r10d NDK which fixes this issue.\n\nR\u003dprimiano@chromium.org\n\nReview URL: https://codereview.chromium.org/1291983003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1495 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "0ad58e6f57ada0f1a9f1b640b5c590dec3a97d87", "tree": "a3da76eff1afaebb7af93316fd28744cebcdeb75", "parents": [ "bdb4b7c617027b82830fa24f15214efac26f2262" ], "author": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Wed Aug 19 22:28:17 2015" }, "committer": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Wed Aug 19 22:28:17 2015" }, "message": "Fix compile error with Windows clang.\n\nThis change fixes the following errors shown during compile with\nWindows clang:\n\nerror: cannot pass non-trivial object of type \u0027ATL::CComBSTR\u0027 to variadic function; expected type from format string was \u0027wchar_t *\u0027 [-Wnon-pod-varargs]\n\nOriginal CL: https://codereview.chromium.org/1252913009/\n\nBUG\u003dhttps://code.google.com/p/google-breakpad/issues/detail?id\u003d662\n\nReview URL: https://codereview.chromium.org/1307463003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1494 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "bdb4b7c617027b82830fa24f15214efac26f2262", "tree": "f368a9d2b70f0e20bbb02045f57f181ae2bfc3de", "parents": [ "c80d21113bfef1b72943823f02f823d8415dd2ba" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Wed Aug 19 07:24:21 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Wed Aug 19 07:24:21 2015" }, "message": "Fix inttypes format macros in src/processor/proc_maps_linux.cc\n\ncrrev.com/1298443002 has introduced a build failure by re-defining\n__STDC_FORMAT_MACROS. Fixing it.\n\nBUG\u003d\nR\u003dmark@chromium.org, ted.mielczarek@gmail.com\n\nReview URL: https://codereview.chromium.org/1303493003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1493 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "c80d21113bfef1b72943823f02f823d8415dd2ba", "tree": "8ff9fa4c555af4e35a5e954f2e29e341ccbf30e4", "parents": [ "6d74ba821fbefb4b7f5bf9444d6e9d4ba627836f" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Aug 18 08:38:14 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Aug 18 08:38:14 2015" }, "message": "Remove obsolete seccomp_unwinder for legacy (pre-BPF) sandbox\n\nThe PopSeccompStackFrame was introduced to deal with stack frames\noriginated in the legacy seccomp sandbox. The only user of that\nsandbox was Google Chrome, but the legacy sandbox has been\ndeprecated in 2013 (crrev.com/1290643003) in favor of the new\nbpf sandbox.\nRemoving this dead code as it has some small bound checking bug\nwhich causes occasional crashes in WebView (which are totally\nunrelated to the sandbox).\n\nNote: this will require a corresponding change in the chromium\nGYP/GN build files to roll.\n\nBUG\u003d665,chromium:477444\nR\u003djln@chromium.org, mark@chromium.org, torne@chromium.org\n\nReview URL: https://codereview.chromium.org/1299593003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1492 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "6d74ba821fbefb4b7f5bf9444d6e9d4ba627836f", "tree": "7af4684996fce87f609db44a259d6260da8b070a", "parents": [ "80cfa0509e1a278dba9aeaa0c0ac6258efdedbae" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Aug 17 11:55:15 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Aug 17 11:55:15 2015" }, "message": "Fix proc_maps_linux compile for non-Linux\n\nR\u003divanpe at https://codereview.chromium.org/1298443002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1491 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "80cfa0509e1a278dba9aeaa0c0ac6258efdedbae", "tree": "bf4a18e869c512de6cc144f056121b1a8db3a25b", "parents": [ "947c7e997f71825c4859db51ce76a0134d4c9ec6" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Aug 17 10:32:26 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Aug 17 10:32:26 2015" }, "message": "[microdump] Move microdump writes to the crash ring-buffer log\n\nSo far the microdump_writer dumped the log in logcat using the default\nsystem log. This is simple to achieve but has some drawbacks:\n 1. Creates spam in the system log, pushing back other eventual useful\n messages.\n 2. There is a high chance that the microdump gets lost if some log\n spam storm happens immediately after a crash and before the log\n is collected by the feedback client.\n 3. Since Android L, the logger is smartly throttling messages (to\n reduce logcat spam). Throttling brekpad logs defeats the all\n point of microdumps.\n\nThis change is conceptually very simple. Replace the use of\n__android_log_write() with __android_log_buf_write(), which takes\nan extra bufID argument. The main drawback is that the\n__android_log_buf_write is not exported in the NDK and needs to be\ndynamically looked up via dlsym.\nThis choice has been discussed and advocated by Android owners.\nSee the internal bug b/21753476.\n\nBUG\u003dchromium:512755\nR\u003dthestig@chromium.org\n\nReview URL: https://codereview.chromium.org/1286063003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1490 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "947c7e997f71825c4859db51ce76a0134d4c9ec6", "tree": "88aa83eb489d5a50e6fd60d7353906218bf9ca02", "parents": [ "d4a69032eef7015912d4d04ab49165b136815625" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Aug 17 08:02:16 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Aug 17 08:02:16 2015" }, "message": "[microdump] Fix hw architecture indication in build fingerprint line\n\nr1456 introduced the possibility to customize the OS-line of the\nmicrodump, enabling to replace, in the case of android, the generic\nuname() info with the Android build fingerprint.\nWhile doing that, it mistakenly removed the HW architecture indication\nfrom the format.\nSee crbug.com/520075 for more details.\n\nBUG\u003dchromium:520075\nR\u003dmmandlis@chromium.org, torne@chromium.org\n\nReview URL: https://codereview.chromium.org/1288313002 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1489 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d4a69032eef7015912d4d04ab49165b136815625", "tree": "0be1ffcb2d478989f53261e5c575cce88d5b84a2", "parents": [ "68ad684370479165908b52709a4aca3b86ccb975" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Sat Aug 15 00:37:14 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Sat Aug 15 00:37:14 2015" }, "message": "Add check for executable stack/heap when rating Linux exploitability.\n\nThis CL also consequentially adds a public method to get the number of\nmappings in a Linux minidump.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1291603002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1488 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "68ad684370479165908b52709a4aca3b86ccb975", "tree": "712cba170239ce9294f066aaa4f15e126c26664d", "parents": [ "412d3cf75ad96320150e46aadafc09ed2fae759e" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Sat Aug 15 00:27:27 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Sat Aug 15 00:27:27 2015" }, "message": "Add check to see if stack pointer is off the stack according to the memory\nmappings when rating Linux exploitability.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1286033002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1487 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "412d3cf75ad96320150e46aadafc09ed2fae759e", "tree": "61b6461e82a8e54afef7176b3c415cd18054dd6f", "parents": [ "5fa512becc12d59f58e575d1ea57ed1272e4638e" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Aug 13 20:13:55 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Aug 13 20:13:55 2015" }, "message": "Fix format specifier in proc maps to support 32-bit architectures.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1288323003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1486 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "5fa512becc12d59f58e575d1ea57ed1272e4638e", "tree": "bd76148d2fe2c4f6d7ee89fbf35ab8a2a1eaaefe", "parents": [ "9a19499abbef497adf21807faa1998d275369f05" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 13 19:49:44 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 13 19:49:44 2015" }, "message": "Actually remove removed files\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1485 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "9a19499abbef497adf21807faa1998d275369f05", "tree": "75f40562daa5a37a8208a4349e6701cace32a7bf", "parents": [ "a60185915a478838d050a90c01b10459f2351aa4" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 13 16:38:19 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Aug 13 16:38:19 2015" }, "message": "Remove some old unused code, add a missing include\nR\u003dlei at https://codereview.chromium.org/1211963002\n\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1484 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "a60185915a478838d050a90c01b10459f2351aa4", "tree": "1e20d393dadb6b26a19ee3c66b56df2ee8a5506e", "parents": [ "70e371c9f2b66d5058386ef0c0bbb71f787b8751" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Aug 12 00:53:39 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Aug 12 00:53:39 2015" }, "message": "Fix format specifier in proc maps to support 32-bit architectures.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1280853003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1483 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "70e371c9f2b66d5058386ef0c0bbb71f787b8751", "tree": "4e4338a4f77624c76fb108370b2d3ade829612cf", "parents": [ "d95798e2fd89b36413e69292122c1015705f4225" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Aug 12 00:21:44 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Aug 12 00:21:44 2015" }, "message": "Allow Print() to be called by const instances of MinidumpLinuxMaps and\nMinidumpLinuxMapsList.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1287803002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1482 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d95798e2fd89b36413e69292122c1015705f4225", "tree": "2e0f62c91112e674548ad427366426100a385c4d", "parents": [ "0f5bff6184c4bada845282e6d01c9f4f6708fdb5" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Aug 11 16:05:48 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Aug 11 16:05:48 2015" }, "message": "Change Print method of MinidumpLinuxMaps and MinidumpLinuxMapsList to print\ncontents of /proc/\u003cpid\u003e/maps instead of just the files mapped to memory.\n\nReview URL: https://codereview.chromium.org/1273123002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1481 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "0f5bff6184c4bada845282e6d01c9f4f6708fdb5", "tree": "1d59f4f7af58cdb16536a25b8247a1a9fb8cab7a", "parents": [ "f5039487f7fa7e55d642c4f88212e5a228b8c056" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Aug 10 17:03:29 2015" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Aug 10 17:03:29 2015" }, "message": "Workaround for range map overlaps caused by Android package relocation.\n\nIf there is a range overlap, the cause may be the client correction applied for Android packed relocations. If this is the case, back out the client correction and retry.\n\nPatch from Simon Baldwin \u003csimonb@chromium.org\u003e.\n\nhttps://code.google.com/p/chromium/issues/detail?id\u003d509110\n\nR\u003dsimonb@chromium.org\n\nReview URL: https://codereview.chromium.org/1275173005\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1480 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f5039487f7fa7e55d642c4f88212e5a228b8c056", "tree": "d4050b3d83887ee69942ae084f23ef35a3dea738", "parents": [ "9f4a8eefd0592b2f319a5332557f237181ab92a8" ], "author": { "name": "cjhopman@chromium.org", "email": "cjhopman@chromium.org", "time": "Wed Aug 05 22:48:48 2015" }, "committer": { "name": "cjhopman@chromium.org", "email": "cjhopman@chromium.org", "time": "Wed Aug 05 22:48:48 2015" }, "message": "Fix breakpad for arm on arm64\n\nOn arm64 devices, GETFPREGS fails with errno\u003d\u003dEIO. Ignore those failures\non Android arm builds.\n\nBUG\u003d508324\nR\u003dthestig@chromium.org\n\nReview URL: https://codereview.chromium.org/1268023003 .\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1479 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "9f4a8eefd0592b2f319a5332557f237181ab92a8", "tree": "a9869a91f5e5bac15df8f2e5b8a4e14800e5f3b0", "parents": [ "b00176d896e28227ede26481efc1fda1c1ced1a4" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Fri Jul 31 15:26:39 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Fri Jul 31 15:26:39 2015" }, "message": "Fix potential null pointer dereference.\n\nIf a MinidumpLinuxMapsList was created and destroyed without its Read method,\nthe program would have a segmentation fault because the destructor did not\ncheck for a null maps_ field. Additional changes include additional\nsupplementary null checks, a potential memory leak fix, and some comment\nremoval.\n\nReview URL: https://codereview.chromium.org/1271543002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1478 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "b00176d896e28227ede26481efc1fda1c1ced1a4", "tree": "ad7dc8b32e6d30aed351d9fceeb40a27918d56b2", "parents": [ "5c7459aa27dd79c3ff66540aefdda0230d7ac243" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Jul 29 00:09:22 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Wed Jul 29 00:09:22 2015" }, "message": "Remove unnecessary dependencies.\n\nReview URL: https://codereview.chromium.org/1266493002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1477 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "5c7459aa27dd79c3ff66540aefdda0230d7ac243", "tree": "cbe60ea11f100ae9c8f8a5c41870b6cab1b4a4ae", "parents": [ "78eab62991a0463f44e47a5a47e1bb8a010edb2c" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jul 28 00:53:44 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jul 28 00:53:44 2015" }, "message": "Add support for Linux memory mapping stream and remove ELF header usage\nwhen checking exploitability rating.\n\nLinux minidumps do not support MD_MEMORY_INFO_LIST_STREAM, meaning the\nprocessor cannot retrieve its memory mappings. However, it has its own\nstream, MD_LINUX_MAPS, which contains memory mappings specific to Linux\n(it contains the contents of /proc/self/maps). This CL allows the minidump\nto gather information from the memory mappings for Linux minidumps.\n\nIn addition, exploitability rating for Linux dumps now use memory mappings\ninstead of checking the ELF headers of binaries. The basis for the change\nis that checking the ELF headers requires the minidumps to store the memory\nfrom the ELF headers, while the memory mapping data is already present,\nmeaning the size of a minidump will be unchanged.\n\nAs a result, of removing ELF header analysis, two unit tests have been removed.\nArguably, the cases that those unit tests check do not merit a high\nexploitability rating and do not warrant a solid conclusion that was given\nearlier.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1251593007\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1476 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "78eab62991a0463f44e47a5a47e1bb8a010edb2c", "tree": "02db47eae091fe3b478d1f11f7f8ceed2d344c74", "parents": [ "d5ca70c72dffc28e90d6e6b09f4abd135ad232fb" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Mon Jul 27 18:04:54 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Mon Jul 27 18:04:54 2015" }, "message": "Fix incorrect comment.\n\nThe exploitability rating for a dump is EXPLOITABILITY_NOT_ANALYZED if the\nexploitability engine in not enabled, not EXPLOITABILITY_NONE.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1254333002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1475 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d5ca70c72dffc28e90d6e6b09f4abd135ad232fb", "tree": "1a2b269ecaa8ba99986543d136ae6ce2fe648441", "parents": [ "f9d81bb8ea2fb0820d18237ba07144a3c3cab135" ], "author": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Mon Jul 20 10:21:27 2015" }, "committer": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Mon Jul 20 10:21:27 2015" }, "message": "add aarch64 support to minidump-2-core\n\nThe thread info expects the struct names as they expect in asm/ptrace.h,\nbut the header doesn\u0027t include that, it includes sys/user.h. Rename the\nreg structs to match that header.\n\nRename the elf_siginfo to _elf_siginfo to avoid conflicting with the one\nin the sys/procfs.h. It is only used locally in one place, so we don\u0027t\nneed to update any callers.\n\nOtherwise, drop in aarch64 support into the minidump-2-core file.\n\nBUG\u003dchromium:334368\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1474 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f9d81bb8ea2fb0820d18237ba07144a3c3cab135", "tree": "b12cdabd5c8ae24c3cd60cc4c95cd5dfd155c1bd", "parents": [ "31916e7e4922e24ede85cbe80b57dbbce1c7170f" ], "author": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Mon Jul 20 06:19:49 2015" }, "committer": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Mon Jul 20 06:19:49 2015" }, "message": "tests: InstructionPointerMemoryNullPointer: make it work under llvm\n\nWhen LLVM sees an attempt to dereference a NULL pointer, it will generate\ninvalid opcodes (undefined behavior) which leads to SIGILL which breaks\nthis unittest. Upstream\u0027s recommendation in this case is to add volatile\nmarkings to get the actual dereference to happen.\n\nThis is documented in the blog post under \"Dereferencing a NULL Pointer\":\nhttp://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1473 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "31916e7e4922e24ede85cbe80b57dbbce1c7170f", "tree": "5455530dba9ba4699f551cf1f43e2085318e5cab", "parents": [ "242fb9a38db6ba534b1f7daa341dd4d79171658b" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Jul 16 20:42:29 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Jul 16 20:42:29 2015" }, "message": "Add ELF header analysis when checking for instruction pointer in code.\n\nIf the minidump module containing the instruction pointer has memory\ncontaining the ELF header and program header table, when checking the\nexploitability rating, the processor will use the ELF header data to determine\nif the instruction pointer lies in an executable region of the module, rather\nthan just checking if it lies in a module.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1233973002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1472 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "242fb9a38db6ba534b1f7daa341dd4d79171658b", "tree": "b46f0e9c8f85a674202ba7dc9029fec52ceb7ef8", "parents": [ "92378d3c29e4d21d3bc6ffddd364ab7c0d03f2fe" ], "author": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Fri Jul 10 20:24:33 2015" }, "committer": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Fri Jul 10 20:24:33 2015" }, "message": "Fix -Wreorder warnings in the Windows code.\n\nThis makes the order of fields in constructor initializer lists match\nthe order in which the fields are declared in (which is the order\nthey\u0027re initialized in). No intended behavior change.\n\nThis change was originally reviewed at\nhttps://codereview.chromium.org/1230923005/\n\nBUG\u003dchromium:505304\nTBR\u003dthakis@chromium.org\n\nReview URL: https://codereview.chromium.org/1234653002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1471 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "92378d3c29e4d21d3bc6ffddd364ab7c0d03f2fe", "tree": "edd5839c7ee3461e98703d23a4aa88dcb889b505", "parents": [ "369160b9cdf9007dede00302e62de487eae031d7" ], "author": { "name": "changluo@google.com", "email": "changluo@google.com", "time": "Fri Jul 10 01:29:50 2015" }, "committer": { "name": "changluo@google.com", "email": "changluo@google.com", "time": "Fri Jul 10 01:29:50 2015" }, "message": "Default nil or empty version string to CFBundleVersion\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1470 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "369160b9cdf9007dede00302e62de487eae031d7", "tree": "ce7a046f3e031992a14a5f821a63f7afce8836f7", "parents": [ "f3aca1f13ce1deeff113ba566e1d2a4359d30313" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jul 07 21:30:06 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jul 07 21:30:06 2015" }, "message": "Set exception whitelist check as earlier check instead of last check.\n\nWhen I first added the exception whitelist, I meant to put the check before\nchecking the location of the instruction pointer. (I didn\u0027t notice that it\nwas after the other check until now.) The whitelist check is to quickly rule\nout minidumps, and if checking the instruction pointer provided any useful\ninformation, it would be pretty indicative that the exception causing the\ndump is interesting.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1211253009\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1469 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f3aca1f13ce1deeff113ba566e1d2a4359d30313", "tree": "98ba5301a75fa1fbca9156da1796645d85ed6026", "parents": [ "276f95d2f651e614c59506d8e8fd95127ddc273f" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 23:22:09 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 23:22:09 2015" }, "message": "Use general instruction/stack pointer convenience method instead of manually\nfinding the instruction/stack pointer for exploitability rating.\n\nThere was already a method that found the instruction pointer, so the files\nfor exploitability ratings had repeated code. Also a method for finding the\nstack pointer is implemented in this CL.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1210943005\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1468 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "276f95d2f651e614c59506d8e8fd95127ddc273f", "tree": "4cb56333ae8b0f0579475844db0b46d3aa15a680", "parents": [ "31500223ca3217ecb9bd945044324934ba551f0b" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 20:34:39 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 20:34:39 2015" }, "message": "Checking for benign exceptions that trigger a minidump.\n\nIf the exception reponsible for the crash is benign, such as a floating point\nexception, we can rule out the possibility that the code is exploitable. This\nCL checks for such exceptions and marks the dump as not exploitable if such an\nexception is found.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1212383004\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1467 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "31500223ca3217ecb9bd945044324934ba551f0b", "tree": "cb203eeeb3bdeae299087a1427829ba6dde13b53", "parents": [ "0bccfcc38087bf8b71c04befe6cd83c683db980a" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 18:17:23 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Tue Jun 30 18:17:23 2015" }, "message": "This CL adds support for ARM and ARM64 architectures when calculating\nexploitability ratings.\n\nThe stackwalker will now grab the instruction pointers for ARM and ARM64\narchitectures, so checking exploitability on ARM and ARM64 will no longer\nreturn EXPLOITABILITY_ERR_PROCESSING.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1216063004\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1466 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "0bccfcc38087bf8b71c04befe6cd83c683db980a", "tree": "1d27a56b0435ce1a8bbd76309490ee867eb2d21a", "parents": [ "dd64e34c8aa926ed363a3b7d1c69ce2885e45d17" ], "author": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Tue Jun 30 13:30:22 2015" }, "committer": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Tue Jun 30 13:30:22 2015" }, "message": "Adjust breakpad module size to match adjusted start_addr.\n\nWhen changing a module\u0027s start_addr to account for Android packed\nrelocations, also adjust its size field so that the apparent module\nend addr calculated by the breakpad processor does not alter.\n\nEnsures that the mapping entry from a packed library is consistent\nwith that which an unpacked one would produce.\n\nBUG\u003d499747\nR\u003dprimiano@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://codereview.chromium.org/1211863002.\n\nPatch from Simon Baldwin \u003csimonb@chromium.org\u003e.\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1465 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "dd64e34c8aa926ed363a3b7d1c69ce2885e45d17", "tree": "66f0942895bd58fdc011810b611e4656d9e7bf98", "parents": [ "5262f18105b41c3868c0b25026e017d6f5ed04af" ], "author": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Jun 25 23:05:16 2015" }, "committer": { "name": "Liu.andrew.x@gmail.com", "email": "Liu.andrew.x@gmail.com", "time": "Thu Jun 25 23:05:16 2015" }, "message": "Checking location of the instruction pointer to see if it is\nin valid code for Linux exploitability rating.\n\nThis CL adds to the Linux exploitability checker by verifying that the\ninstruction pointer is in valid code. Verification is done by obtaining a\nmemory mapping of the crash and checking if the instruction pointer lies in\nan executable region. If there is no memory mapping, the instruction pointer\nis checked to determine if it lies within a known module.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://codereview.chromium.org/1210493003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1464 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "5262f18105b41c3868c0b25026e017d6f5ed04af", "tree": "c80cc544b650975e0725c5334371a84454345b07", "parents": [ "32f4fb03210de1bca01bda9ceaf7fbbdaba98aaa" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Jun 22 21:21:40 2015" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Jun 22 21:21:40 2015" }, "message": "Reconfigured options for sym_upload to not treat h and ? flags as invalid options.\n\nI\u0027m submitting this on behalf of Andrew Liu.\n\nR\u003dmmandlis@chromium.org\n\nReview URL: https://codereview.chromium.org/1196733004\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1462 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "32f4fb03210de1bca01bda9ceaf7fbbdaba98aaa", "tree": "96d97f25d43a1c167344b9717a18cf34ea8b6c55", "parents": [ "f90fa7241fd703a1dfddebe57c1e6d3c730c2a95" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Jun 22 11:50:00 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Jun 22 11:50:00 2015" }, "message": "Fix signal propagation logic for Linux/Android exception handler.\n\nThe current code is relying on info-\u003esi_pid to figure out whether\nthe exception handler was triggered by a signal coming from the kernel\n(that will re-trigger until the cause that triggered the signal has\nbeen cleared) or from user-space e.g., kill -SIGNAL pid, which will NOT\nautomatically re-trigger in the next signal handler in the chain.\nWhile the intentions are good (manually re-triggering user-space\nsignals), the current implementation mistakenly looks at the si_pid\nfield in siginfo_t, assuming that it is coming from the kernel if\nsi_pid \u003d\u003d 0.\nThis is wrong. siginfo_t, in fact, is a union and si_pid is meaningful\nonly for userspace signals. For signals originated by the kernel,\ninstead, si_pid overlaps with si_addr (the faulting address).\nAs a matter of facts, the current implementation is mistakenly\nre-triggering the signal using tgkill for most of the kernel-space\nsignals (unless the fault address is exactly 0x0).\nThis is not completelly correct for the case of SIGSEGV/SIGBUS. The\nnext handler in the chain will stil see the signal, but the |siginfo|\nand the |context| arguments of the handler will be meaningless\n(retriggering a signal with tgkill doesn\u0027t preserve them).\nTherefore, if the next handler in the chain expects those arguments\nto be set, it will fail.\nConcretelly, this is causing problems to WebView. In some rare\ncircumstances, the next handler in the chain is a user-space runtime\nwhich does SIGSEGV handling to implement speculative null pointer\nmanaged exceptions (see as an example\nhttp://www.mono-project.com/docs/advanced/runtime/docs/exception-handling/)\n\nThe fix herein proposed consists in using the si_code (see SI_FROMUSER\nmacros) to determine whether a signal is coming form the kernel\n(and therefore just re-establish the next signal handler) or from\nuserspace (and use the tgkill logic).\n\nRepro case:\nThis issue is visible in Chrome for Android with this simple repro case:\n- Add a non-null pointer dereference in the codebase:\n *((volatile int*)0xbeef) \u003d 42\nWithout this change: the next handler (the libc trap) prints:\n F/libc ( 595): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x487\n where 0x487 is actually the PID of the process (which is wrong).\nWith this change: the next handler prints:\n F/libc ( 595): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xbeef\n which is the correct answer.\n\nBUG\u003dchromium:481937\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/6844002.\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1461 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f90fa7241fd703a1dfddebe57c1e6d3c730c2a95", "tree": "04da086c64c40c5ef8b8eb2889d071145f8269ea", "parents": [ "01c68857760e7c1bcee45942742de929b520376f" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Sat Jun 20 00:32:37 2015" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Sat Jun 20 00:32:37 2015" }, "message": "Use local variable for out parameter rather than direct use of ivar\n\n- Resolves spurious static analyzer warning about response_ being potentially leaked due to the retain in Xcode 6.3 and later.\n\nI\u0027m submitting this on behalf of Brian Moore.\n\nR\u003dqsr@chromium.org\n\nReview URL: https://codereview.chromium.org/1171693007\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1460 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "01c68857760e7c1bcee45942742de929b520376f", "tree": "1395cbd7e9431f157963f2c7cbe6475851760f46", "parents": [ "288ba54a587bf1671d7ecdf9de925615d4618053" ], "author": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Fri Jun 19 16:30:42 2015" }, "committer": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Fri Jun 19 16:30:42 2015" }, "message": "Update breakpad for Android packed relocations.\n\nShared libraries containing Android packed relocations have a load\nbias that differs from the start address in /proc/$$/maps. Current\nbreakpad assumes that the load bias and mapping start address are\nthe same.\n\nFixed by changing the client to detect the presence of Android packed\nrelocations in the address space of a loaded library, and adjusting the\nstored mapping start address of any that are packed so that it contains\nthe linker\u0027s load bias.\n\nFor this to work properly, it is important that the non-packed library\nis symbolized for breakpad. Either packed or non-packed libraries may\nbe run on the device; the client detects which has been loaded by the\nlinker.\n\nBUG\u003d499747\nR\u003dprimiano@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://codereview.chromium.org/1189823002.\n\nPatch from Simon Baldwin \u003csimonb@chromium.org\u003e.\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1459 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "288ba54a587bf1671d7ecdf9de925615d4618053", "tree": "fd7550c7a0e480e8495c75afbc82abda627fd5c6", "parents": [ "d7e4030ff7d38e0d88d7ca39c1c1222940bfb3b7" ], "author": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Thu May 28 06:16:15 2015" }, "committer": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Thu May 28 06:16:15 2015" }, "message": "update more ignore files\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1458 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d7e4030ff7d38e0d88d7ca39c1c1222940bfb3b7", "tree": "fd7550c7a0e480e8495c75afbc82abda627fd5c6", "parents": [ "9fcbe255a64d39295ad5f1f15c0b92db3da83c0f" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri May 15 08:43:01 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri May 15 08:43:01 2015" }, "message": "[microdump] Add build fingerprint and product info metadata.\n\nThis is to add build fingerprint and product name/version to\nmicrodumps. Conversely to what happens in the case of minidumps\nwith MIME fields, due to the nature of minidumps, extra metadata\ncannot be reliably injected after the dump is completed.\nThis CL adds the plumbing to inject two optional fields plus the\ncorresponding tests.\n\nBUG\u003dchromium:410294\nR\u003dthestig@chromium.org\n\nReview URL: https://codereview.chromium.org/1125153008\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1456 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "9fcbe255a64d39295ad5f1f15c0b92db3da83c0f", "tree": "4e8225e83d2641675e878ec4cb3265eda0b856df", "parents": [ "fa5a6b3449dbe77a107a891b96c0e47387302e2e" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Thu Apr 30 09:12:54 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Thu Apr 30 09:12:54 2015" }, "message": "Fix signal propagation logic for Linux/Android exception handler.\n\nThe current code is relying on info-\u003esi_pid to figure out whether\nthe exception handler was triggered by a signal coming from the kernel\n(that will re-trigger until the cause that triggered the signal has\nbeen cleared) or from user-space e.g., kill -SIGNAL pid, which will NOT\nautomatically re-trigger in the next signal handler in the chain.\nWhile the intentions are good (manually re-triggering user-space\nsignals), the current implementation mistakenly looks at the si_pid\nfield in siginfo_t, assuming that it is coming from the kernel if\nsi_pid \u003d\u003d 0.\nThis is wrong. siginfo_t, in fact, is a union and si_pid is meaningful\nonly for userspace signals. For signals originated by the kernel,\ninstead, si_pid overlaps with si_addr (the faulting address).\nAs a matter of facts, the current implementation is mistakenly\nre-triggering the signal using tgkill for most of the kernel-space\nsignals (unless the fault address is exactly 0x0).\nThis is not completelly correct for the case of SIGSEGV/SIGBUS. The\nnext handler in the chain will stil see the signal, but the |siginfo|\nand the |context| arguments of the handler will be meaningless\n(retriggering a signal with tgkill doesn\u0027t preserve them).\nTherefore, if the next handler in the chain expects those arguments\nto be set, it will fail.\nConcretelly, this is causing problems to WebView. In some rare\ncircumstances, the next handler in the chain is a user-space runtime\nwhich does SIGSEGV handling to implement speculative null pointer\nmanaged exceptions (see as an example\nhttp://www.mono-project.com/docs/advanced/runtime/docs/exception-handling/)\n\nThe fix herein proposed consists in using the si_code (see SI_FROMUSER\nmacros) to determine whether a signal is coming form the kernel\n(and therefore just re-establish the next signal handler) or from\nuserspace (and use the tgkill logic).\n\nRepro case:\nThis issue is visible in Chrome for Android with this simple repro case:\n- Add a non-null pointer dereference in the codebase:\n *((volatile int*)0xbeef) \u003d 42\nWithout this change: the next handler (the libc trap) prints:\n F/libc ( 595): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x487\n where 0x487 is actually the PID of the process (which is wrong).\nWith this change: the next handler prints:\n F/libc ( 595): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xbeef\n which is the correct answer.\n\nBUG\u003dchromium:481937\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/6844002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1454 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "fa5a6b3449dbe77a107a891b96c0e47387302e2e", "tree": "55c22c55745a961936ebccc346b70123d99df395", "parents": [ "328d128ed96bfdd326aeebf96c63a4b97a69ee8f" ], "author": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Wed Apr 22 20:14:24 2015" }, "committer": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Wed Apr 22 20:14:24 2015" }, "message": "Support object files larger than 2**32.\n\nReviewed at https://breakpad.appspot.com/7834002/#ps340001\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1453 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "328d128ed96bfdd326aeebf96c63a4b97a69ee8f", "tree": "41da57ec2376d3b34147b672aa9e317e29b9e6f3", "parents": [ "dbc7f3c45f0df562304eb5ef49a7c7125e076c8d" ], "author": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Tue Apr 21 21:34:14 2015" }, "committer": { "name": "rmcilroy@chromium.org", "email": "rmcilroy@chromium.org", "time": "Tue Apr 21 21:34:14 2015" }, "message": "[MIPS]: Use mcontext_t structure for MIPS\n\nThis change removes user_regs_struct and\nuser_fpregs_struct structures for mips\nand uses mcontext_t instead.\n\nR\u003dfdegans@chromium.org, mark@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://breakpad.appspot.com/3744002\n\nPatch from Gordana Cmiljanovic \u003cGordana.Cmiljanovic@imgtec.com\u003e.\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1452 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "dbc7f3c45f0df562304eb5ef49a7c7125e076c8d", "tree": "8d52c0ab5eb9dfb0acb53c7f00fd1285b5c1a623", "parents": [ "ad88d965aa35dabdfe0cded39f72dde9e4a3591e" ], "author": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Sat Apr 18 03:27:45 2015" }, "committer": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Sat Apr 18 03:27:45 2015" }, "message": "update svn:ignores\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1451 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "ad88d965aa35dabdfe0cded39f72dde9e4a3591e", "tree": "8d52c0ab5eb9dfb0acb53c7f00fd1285b5c1a623", "parents": [ "3f8a019307e63392f257a74f4072ef88f60fe549" ], "author": { "name": "cjhopman@chromium.org", "email": "cjhopman@chromium.org", "time": "Wed Apr 15 22:57:24 2015" }, "committer": { "name": "cjhopman@chromium.org", "email": "cjhopman@chromium.org", "time": "Wed Apr 15 22:57:24 2015" }, "message": "Fix call to rt_sigaction\n\nDespite the fact that many places imply that sigaction and rt_sigaction\nare essentially the same, rt_sigaction\u0027s signature is actually\ndifferent-- it takes the size of the kernel\u0027s sigset_t as an extra argument.\n\nBUG\u003d473973\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1447 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "3f8a019307e63392f257a74f4072ef88f60fe549", "tree": "c4973e27da5a6eb01986394834e14ab63caefd05", "parents": [ "ecf9e2b4d58848e3abd45af16692c0740d272bc3" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Apr 15 19:28:11 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Apr 15 19:28:11 2015" }, "message": "MIPS64: Initial MIPS64 related change.\n\nWith this change Breakpad can be compiled for MIPS64,\nbut it is not yet functional.\n\nPatch by Gordana Cmiljanovic \u003cGordana.Cmiljanovic@imgtec.com\u003e\nReview URL: https://breakpad.appspot.com/6824002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1446 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "ecf9e2b4d58848e3abd45af16692c0740d272bc3", "tree": "653f3315fd55c41e2e666471b53091423bdea15d", "parents": [ "b8a7ea6d4b2de9ef00f375696c718b5309f4e3d0" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Mon Apr 13 23:59:06 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Mon Apr 13 23:59:06 2015" }, "message": "Use __NR_rt_sigaction instead of __NR_sigaction\n\n__NR_sigaction is not defined on arm64/x64/etc (or rather, it\u0027s defined\nin unistd-32.h instead of unistd.h).\n\nPatch by Chris Hopman \u003ccjhopman@chromium.org\u003e\nReview URL: https://breakpad.appspot.com/10724002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1443 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "b8a7ea6d4b2de9ef00f375696c718b5309f4e3d0", "tree": "d01e16d122d7b0d3fac8d39506cbbb0e1b505cd8", "parents": [ "d0b34abafbf97ec594cc5ea851c2ccbfd2a0f2f8" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Apr 13 17:45:17 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Apr 13 17:45:17 2015" }, "message": "Microdump processor: be more tolerant for different logcat formats\n\nThe current processor implementation is grepping for /google-breakpad(\nin the logcat lines, to filter out microdump lines, which by default\nlook like this:\nW/google-breakpad( 3728): -----BEGIN BREAKPAD MICRODUMP-----\n\nTurns out that logcat format can vary, when passing optional arguments,\nand produce something like the following:\n\n04-13 12:30:35.563 6531 6531 W google-breakpad: -----BEGIN ...\n\nIn the latter case, the \"/google-breakpad(\" filter is too aggressive.\nThis change is relaxing it, so it is compatible also with non-default\nlogcat arguments.\n\nBUG\u003d640\nR\u003dmmandlis@chromium.org\n\nReview URL: https://breakpad.appspot.com/2864002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1442 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d0b34abafbf97ec594cc5ea851c2ccbfd2a0f2f8", "tree": "91cdec6c24139fd63ec42938f4b951c9df8a8979", "parents": [ "16c6ed288ec3cc5dd39ed6f4b12e8764e6709d9c" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Fri Apr 10 22:05:29 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Fri Apr 10 22:05:29 2015" }, "message": "Add address and reason for IN_PAGE_ERROR.\n\nACCESS_VIOLATION and IN_PAGE_ERROR both specify\nread/write/dep flags and address. ACCESS_VIOLATION currently\nreports these, but IN_PAGE_ERROR does not. This change makes\nIN_PAGE_ERROR report this information as well, and also the\nadditional NTSTATUS value for the underlying cause.\n\nPatch by bungeman@chromium.org\nReview URL: https://breakpad.appspot.com/1794002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1441 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "16c6ed288ec3cc5dd39ed6f4b12e8764e6709d9c", "tree": "b1d21f1a23fb1e8339ca3575b228cf592c9ef11d", "parents": [ "8828713d637acb68a04a9c229e163dd79170173f" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Fri Apr 10 17:57:24 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Fri Apr 10 17:57:24 2015" }, "message": "Workaround Android sigaction bug\n\nOn Android L+, signal and sigaction symbols are provided by libsigchain\nthat override the system\u0027s versions. There is a bug in these functions\nwhere they essentially ignore requests to install SIG_DFL.\n\nWorkaround this issue by explicitly performing a syscall to\n__NR_rt_sigaction to install SIG_DFL on Android.\n\nBUG\u003d473973\n\nPatch by Chris Hopman \u003ccjhopman@chromium.org\u003e\nReview URL: https://breakpad.appspot.com/1804002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1438 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "8828713d637acb68a04a9c229e163dd79170173f", "tree": "c28b3bccbef453f50eece9f33c2ccf29c1e6936e", "parents": [ "2c37c225e729d6ada72d5ffd808406db9c916985" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Tue Mar 24 11:25:14 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Tue Mar 24 11:25:14 2015" }, "message": "Fix compilation with gcc --std\u003dc++11\nPatch by Jon Turney \u003cjon.turney.1111@gmail.com\u003e\nR\u003dted at https://breakpad.appspot.com/7824002/\n\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1435 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "2c37c225e729d6ada72d5ffd808406db9c916985", "tree": "5321426c378868067fb9f83b6513377e936095b6", "parents": [ "ac07e580b221a22c08e9398cd15744870521b364" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Mar 16 14:12:20 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Mon Mar 16 14:12:20 2015" }, "message": "Fix compatibility with Android NDK r10d.\n\nThis is a reland of the previous CL (r1433). r1433 did not achieve what\nintended and failed the x86_64 build of Chrome with NDK r10c.\nThe workaround logic in this CL is identical to r1433, but the #define\nmagic is applied in a more appropriate proper place this time. Turns\nout Breakpad already has an Android compatibility layer, which is\ncommon/android/include. Piggybacking the fix there.\n\nBUG\u003dbreakpad:642\nR\u003dfdegans@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://breakpad.appspot.com/3794002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1434 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "ac07e580b221a22c08e9398cd15744870521b364", "tree": "59940f48d7e478b7e9ffc9b5bcf5b012930ae175", "parents": [ "d1f8b74d65c28d29e8e75df7d70780ec7f6e9216" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Mar 10 20:09:06 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Mar 10 20:09:06 2015" }, "message": "Make breakpad compatible with Android NDK r10d.\n\nr1397 did introduce a workaround to deal with a typo in sys/user.h\nin the Android NDK. The typo has been fixed in [1]. However, breakpad\ncannot just switch to the fixed version as this would require atomic\nrolls of Breakpad and NDK in chromium, which would make reverts hard\nto handle.\nThis change introduces an inelegant yet functional hack which makes\nbreakpad compatible with both versions of the NDK, with and without\nthe typo. It can be reverted once Chrome has stably rolled to NDK\nr10d.\n\n[1] https://android.googlesource.com/platform/bionic/+/f485547b\n\nBUG\u003dbreakpad:642\nR\u003dfdegans@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://breakpad.appspot.com/7814002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1433 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d1f8b74d65c28d29e8e75df7d70780ec7f6e9216", "tree": "9d43589068c6bae3eee891c147e81b632cce010f", "parents": [ "2e35bbb2b9b76142824ef7945e51b16ca906c4e6" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Mar 10 20:06:04 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Mar 10 20:06:04 2015" }, "message": "Microdump writer: stop using new/malloc in compromised context\n\nA recent change in the client-side microdump write (r1404) ended up\nintroducing a call to new() to instantiate the line buffer that\nmicrodump uses to dump its lines. new/malloc is a luxury we cannot\nafford in a compromised context.\nThis change switches the line buffer to be backed by the dumper\npage allocator, which on Linux/Android ends up requesting pages\nvia mmap.\nAlso, the microdump write bails out without crashing if the page\nallocator failed (crash during severe OOM).\n\nBUG\u003d640\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1432 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "2e35bbb2b9b76142824ef7945e51b16ca906c4e6", "tree": "361ced6968ab8028d674942d6e6edb3a5f014f2b", "parents": [ "0a0ad99fc889b40623a8880e767995905af44abc" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Fri Mar 06 20:12:00 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Fri Mar 06 20:12:00 2015" }, "message": "Fix Windows dump_syms x64 linking\n\nThe dia_sdk GYP target points at the x86 diaguids.lib, it needs to\npoint at the x64 one for x64 builds.\nR\u003dmark at https://breakpad.appspot.com/9784002/\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1431 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "0a0ad99fc889b40623a8880e767995905af44abc", "tree": "8faa98a1c139f354ffd66ca2d2fc770ef07c3b6c", "parents": [ "36028d5e9cd66078c54a0fb707a400743bea9fd0" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Fri Feb 27 13:40:41 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Fri Feb 27 13:40:41 2015" }, "message": "Formatting tweak for https://breakpad.appspot.com/9774002, add more newlines\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1430 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "36028d5e9cd66078c54a0fb707a400743bea9fd0", "tree": "76128fd47e305aa4ee8b63960e60a65293fbdba5", "parents": [ "faf5994b2f268d18ab694260b3339c7f98f03802" ], "author": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Fri Feb 27 04:52:21 2015" }, "committer": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Fri Feb 27 04:52:21 2015" }, "message": "Add stack contents output functionality to minidump_stackwalk\n\nThis feature is enabled only when \"-s\" is provided as a commandline option.\n\nminidump_stackwalk.cc:\n - Add a new commandline option \"-s\" to output stack contents.\n - Instantiate Minidump object in PrintMinidumpProcess() to keep it alive longer so that accessing process_state.thread_memory_regions() in stackwalk_common.cc doesn\u0027t result in use-after-free.\n\nstackwalk_common.cc:\n - Add a new function PrintStackContents() to output stack contents.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/9774002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1429 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "faf5994b2f268d18ab694260b3339c7f98f03802", "tree": "e4eaa6b9503a66b401720c0570a008e81d35edea", "parents": [ "764522eb3d1bca3d8efcd169037269b54f2564d7" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Feb 25 21:16:43 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Feb 25 21:16:43 2015" }, "message": "Update license on convert_UTF.* to the standard Unicode license.\n\nBUG\u003dgoogle-breakpad:270\nR\u003dted.mielczarek@gmail.com\n\nReview URL: https://breakpad.appspot.com/9764002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1428 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "764522eb3d1bca3d8efcd169037269b54f2564d7", "tree": "b4b70790b0f1035313667c26f079fbca92d7c7ac", "parents": [ "f6875ca80deaf1a284b4172ad3dcfd7bb7b188f3" ], "author": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Sun Feb 22 02:27:35 2015" }, "committer": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Sun Feb 22 02:27:35 2015" }, "message": "Add option to Breakpad to consume INVALID_HANDLE_VALUE exceptions.\n\nBUG\u003dchromium:452613\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/7794002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1427 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f6875ca80deaf1a284b4172ad3dcfd7bb7b188f3", "tree": "c84d1c0ddf702082e510db7feb22224d3e7551b5", "parents": [ "09460c7d810d244550d3365c01af2731be2b347b" ], "author": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Tue Feb 10 22:36:39 2015" }, "committer": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Tue Feb 10 22:36:39 2015" }, "message": "Cleanup Linux debug link file handling code.\n\n- Handle the case when the debug link points back to the object file.\n- Move some checks into a separate SanitizeDebugFile() function.\n\nBUG\u003d636\nReview URL: https://breakpad.appspot.com/3784002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1426 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "09460c7d810d244550d3365c01af2731be2b347b", "tree": "c4648afec766139d850c234ca14fd8ce2ab6d308", "parents": [ "9172781ec43ce635214f5cbb73bf9cd482bd1df3" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Thu Feb 05 23:01:31 2015" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Thu Feb 05 23:01:31 2015" }, "message": "Fix overflow error in breakpad for linux\n\nA computation in the stack unwind algorithm could cause an overflow if a base\npointer read from crashed process is sufficiently close to top of address space.\nThis causes a memory read that causes the dump thread to crash, resulting in a\nfailure to generate crash dump. Check fixed to properly detect that this pointer\nis greater than actual memory range of current stack.\n\nPatch by Kyle Joswiak \u003ckjoswiak@chromium.org\u003e\n\nReview URL: https://breakpad.appspot.com/3754003/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1425 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "9172781ec43ce635214f5cbb73bf9cd482bd1df3", "tree": "699ddd9628550bcf089756220cc2b7f0352ba0f0", "parents": [ "81794ad461cecf8901faf501b850b7da10cd9020" ], "author": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Wed Feb 04 00:03:58 2015" }, "committer": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Wed Feb 04 00:03:58 2015" }, "message": "Add unit tests for overlapping functions and externs.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/3774002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1424 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "81794ad461cecf8901faf501b850b7da10cd9020", "tree": "0950c4b65185098677bbb901dcc062537695f1f7", "parents": [ "e3e650186fd964c29a4a86639a2c9bcb645b7e80" ], "author": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Tue Feb 03 23:13:04 2015" }, "committer": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Tue Feb 03 23:13:04 2015" }, "message": "Handle ARM THUMB functions when removing duplicate PUBLIC entries.\n\nIn ELF symtab/dynsym sections, THUMB function addresses have bit 0 set,\nwhereas the DWARF function entries are not.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/7774002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1423 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "e3e650186fd964c29a4a86639a2c9bcb645b7e80", "tree": "7e845ec88c527884b70f1c239b6dc6f328d4659f", "parents": [ "f8eed7414397abe3c9c2bf5d48e62e072e96df61" ], "author": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Feb 03 07:16:04 2015" }, "committer": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Feb 03 07:16:04 2015" }, "message": "Follow debug link correctly\n\nAs thestig@chromium.org pointed out in https://breakpad.appspot.com/9684002,\nLoadSymbols() should return false if |read_gnu_debug_link| is false.\n\nBUG\u003dchromium:453498\nR\u003dthestig@chromium.org\n\nReview URL: https://breakpad.appspot.com/2844002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1422 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f8eed7414397abe3c9c2bf5d48e62e072e96df61", "tree": "fa93123006e2809d1895b53ceff5394e37220816", "parents": [ "72a1fcfe3c7d250ed10d7662d14470c63b07039d" ], "author": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Feb 03 03:17:30 2015" }, "committer": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Feb 03 03:17:30 2015" }, "message": "Demangle symbol name\n\nThe spec says it should be demangled.\nhttps://code.google.com/p/google-breakpad/wiki/SymbolFiles\n\nBUG\u003dchromium:453498\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/2854002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1421 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "72a1fcfe3c7d250ed10d7662d14470c63b07039d", "tree": "ded7c639586a0095a6e253fd76bc698acdc02cd5", "parents": [ "7b44faad9aa8ed0bcb4fe395359b4d0cac046e23" ], "author": { "name": "benchan@chromium.org", "email": "benchan@chromium.org", "time": "Mon Feb 02 23:27:27 2015" }, "committer": { "name": "benchan@chromium.org", "email": "benchan@chromium.org", "time": "Mon Feb 02 23:27:27 2015" }, "message": "Handle failures of copying process data from a core file.\n\nWhen LinuxCoreDumper fails to copy process data from a core file, it\nfills the return buffer with a repeated sequence of a special marker.\nHowever, MinidumpWriter doesn\u0027t know about that and may incorrectly\ninterpret the data. In many cases, MinidumpWriter simply copies the\ngibberish data to the minidump, which isn\u0027t too bad. However, the\ngibberish data may cause MinidumpWriter to behave badly in some other\ncases. For example, when MinidumpWriter tries to iterate through the\nlinked list of all loaded DSOs via the r_map field of a r_debug struct,\nif the linked list is filed with the special marker, the code keeps\niterating through the same address.\n\nThis CL addresses the issue by having LinuxCoreDumper::CopyFromProcess()\nreturns a Boolean value to indicate if the expected data is found from\nthe core file. MinidumpWriter can then decide how to handle that.\n\nBUG\u003dchromium:453484\nTEST\u003dRun core2md with the test data attached to chromium:453484.\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/4724002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1420 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "7b44faad9aa8ed0bcb4fe395359b4d0cac046e23", "tree": "b9d7503255b4bcb17be53892d5671d61ad3d3a70", "parents": [ "dad63f9804faa640a1ca194710a966f33d8f8818" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Feb 02 14:05:45 2015" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Feb 02 14:05:45 2015" }, "message": "Replace uses of hash_map with unordered_map\n\nhash_map no longer exists in Visual C++ 2015.\nA\u003dBrian Smith \u003cbrian@briansmith.org\u003e\nR\u003dted at https://bugzilla.mozilla.org/show_bug.cgi?id\u003d1119072\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1419 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "dad63f9804faa640a1ca194710a966f33d8f8818", "tree": "05ecf93d3b822bd01b38132f419c81604aff6307", "parents": [ "eb04cd87d04c5be61d4d95695a8d960699576082" ], "author": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Wed Jan 28 21:47:31 2015" }, "committer": { "name": "vapier@chromium.org", "email": "vapier@chromium.org", "time": "Wed Jan 28 21:47:31 2015" }, "message": "Remove unneeded definitions of O_BINARY\n\nReview URL: https://breakpad.appspot.com/6684002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1418 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "eb04cd87d04c5be61d4d95695a8d960699576082", "tree": "5a23e0753502cb95440b8ce0777f933d91402742", "parents": [ "d5d1eacd7394325c27d715a83976a3bb7d4d237f" ], "author": { "name": "benchan@chromium.org", "email": "benchan@chromium.org", "time": "Wed Jan 28 18:33:50 2015" }, "committer": { "name": "benchan@chromium.org", "email": "benchan@chromium.org", "time": "Wed Jan 28 18:33:50 2015" }, "message": "Remove unused variable \u0027kGUIDStringSize\u0027 in microdump_writer_unittest.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/3754002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1417 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d5d1eacd7394325c27d715a83976a3bb7d4d237f", "tree": "c437ee65e9273c9a39b3ebfe448e3cfb650604e7", "parents": [ "482062f6b25dff1b6ede35cdcb81acecdaae026e" ], "author": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Jan 27 03:27:08 2015" }, "committer": { "name": "hashimoto@chromium.org", "email": "hashimoto@chromium.org", "time": "Tue Jan 27 03:27:08 2015" }, "message": "Stop calling memmove when unnecessary\n\nBUG\u003dchromium:450137\nR\u003dmark@chromium.org\n\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1416 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "482062f6b25dff1b6ede35cdcb81acecdaae026e", "tree": "d2a22c05227ccd44f696754cc875c8290558d574", "parents": [ "398c70a3e6825e2bc77fb4779107b018c58f0612" ], "author": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Tue Jan 27 01:20:59 2015" }, "committer": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Tue Jan 27 01:20:59 2015" }, "message": "Fix some fragile code that is likely to cause future memory corruption\nproblems.\n\n- The ordering of keys in stl containers cannot change. Make the relevant\nmembers const to guarantee this assumption.\n- Add handling and logging for demangle errors.\n- Fix a potential double-delete bug if a function passed to AddFunction() is\nalready present.\n\nBUG\u003dchromium:449214\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/10704002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1415 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "398c70a3e6825e2bc77fb4779107b018c58f0612", "tree": "e3cea2d81dc716fe1f718ae775b398d0b6b9bf3d", "parents": [ "58aca2ddf2f7d873b8705886c8cce1b3f68c2bc9" ], "author": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Mon Jan 26 23:19:04 2015" }, "committer": { "name": "erikchen@chromium.org", "email": "erikchen@chromium.org", "time": "Mon Jan 26 23:19:04 2015" }, "message": "Fix a source of memory corruption.\n\nThis error was causing crashes in official Chrome Mac builds on 10.8.5\nmachines.\n\nBUG\u003dchromium:449214\nR\u003dmark@chromium.org\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1414 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "58aca2ddf2f7d873b8705886c8cce1b3f68c2bc9", "tree": "d0ad869cc7bc416f21b9f0d44d2c5f2bf1e6f540", "parents": [ "2e9e298a0af15b737a287ce341f254ae1f982a85" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Jan 09 17:58:19 2015" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Jan 09 17:58:19 2015" }, "message": "Fix the scope on the initialization of kMicrodumpOnConsole to match header.\n\nI whish I knew how this worked for months in chromium as it is clearly wrong.\nAs reported by azarchs@ it is breaking the cygprofile instrumented build.\n\nBUG\u003dchromium:410294\n\nReview URL: https://breakpad.appspot.com/1784002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1413 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "2e9e298a0af15b737a287ce341f254ae1f982a85", "tree": "e743a8a43bd43bef5aff0e4abe063ca8ef333a8b", "parents": [ "8309f9051fb7370fc6f23e098bb7ccbaed4c1680" ], "author": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Sat Dec 20 00:47:07 2014" }, "committer": { "name": "wfh@chromium.org", "email": "wfh@chromium.org", "time": "Sat Dec 20 00:47:07 2014" }, "message": "Modify minidump_stackwalk to be more tolerant of overlapping ranges.\n\nThese ranges can be seen in some Android minidumps.\n\nBUG\u003dchromium:439531\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/9744002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1412 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "8309f9051fb7370fc6f23e098bb7ccbaed4c1680", "tree": "baa1311c720108a8e1ecbc4876086820a5e66d1b", "parents": [ "b1df2ab24006e13cc7169eccd7db89db6f7a7f74" ], "author": { "name": "jessicag.feedback@gmail.com", "email": "jessicag.feedback@gmail.com", "time": "Thu Dec 11 19:30:37 2014" }, "committer": { "name": "jessicag.feedback@gmail.com", "email": "jessicag.feedback@gmail.com", "time": "Thu Dec 11 19:30:37 2014" }, "message": "Add microdump files to project.\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1411 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "b1df2ab24006e13cc7169eccd7db89db6f7a7f74", "tree": "1fd76207d3f5861e9d9bf5faec858ce2a323ffe7", "parents": [ "3a09bb0766eba3ef1766a1617caf1bb5460de85e" ], "author": { "name": "mdempsky@chromium.org", "email": "mdempsky@chromium.org", "time": "Thu Dec 11 01:17:43 2014" }, "committer": { "name": "mdempsky@chromium.org", "email": "mdempsky@chromium.org", "time": "Thu Dec 11 01:17:43 2014" }, "message": "Remove pointers from serialized file format\n\nBUG\u003dbreakpad:621\nR\u003dthestig@chromium.org\n\nReview URL: https://breakpad.appspot.com/1764002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1410 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "3a09bb0766eba3ef1766a1617caf1bb5460de85e", "tree": "dac405e12e94a391550511d41a997483309a8f45", "parents": [ "353da535e9af783c1c3fe896b1b3dc56e75486af" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Dec 10 16:08:09 2014" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Dec 10 16:08:09 2014" }, "message": "Breakpad: Fix build with new clang versions.\n\ngcc has a single exception setting for all languages. Saying -fno-exceptions\nin gcc disables exceptions and cleanups for cc files, but has no effect for mm\nfiles.\n\nIn clang, -fno-exceptions only disables c++ exceptions, but keeps objective-c\nexceptions and cleanups enabled.\n\nhttp://llvm.org/viewvc/llvm-project?view\u003drevision\u0026revision\u003d220714 changed\n__EXCEPTIONS to be defined for clang when cleanups are enabled, independent of\nif c++ exceptions are enabled. (This was necessary to have clang work with\nglibc which looks at __EXCEPTIONS to decide if cleanups are enabled.)\n\nBreakpad tried to use __EXCEPTIONS to figure out if c++ exceptions are enabled.\nIn cc files, this works: -fno-exceptions will disable c++ exceptions and\ncleanups. But in mm files, -fno-exceptions will disable c++ exceptions and\nobjective-c exceptions will still be enabled, and so cleanups must run and hence\n__EXCEPTIONS is defined.\n\nTo make things work with both old and new compilers, do the try/catch hack in\nmm files either if __EXCEPTIONS is not defined (for old compilers) or if the\ncompiler is clang and __has_feature(cxx_exceptions) isn\u0027t set (which will work\nfor new clangs too, and which cleanly maps to if c++ exceptions are enabled).\n\nPatch by Nico Weber \u003cthakis@chromium.org\u003e\n\nReview URL: https://breakpad.appspot.com/1774002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1409 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "353da535e9af783c1c3fe896b1b3dc56e75486af", "tree": "9544236fd46788ab661eb0b81d899affa7573851", "parents": [ "57c3d7c9f1f86525f120337b47d6ebd586215e1e" ], "author": { "name": "mseaborn@chromium.org", "email": "mseaborn@chromium.org", "time": "Wed Dec 03 20:39:55 2014" }, "committer": { "name": "mseaborn@chromium.org", "email": "mseaborn@chromium.org", "time": "Wed Dec 03 20:39:55 2014" }, "message": "dump_syms: Fix handling of DW_FORM_ref_addr to work with DWARF 4\n\nPreviously, dump_syms did not handle DW_FORM_ref_addr if it appeared\nin DWARF 4 debugging info.\n\nAlso fix a DW_FORM_ref_addr case so that it doesn\u0027t fall through to\nthe next switch case when assertions are disabled and the DWARF\nversion isn\u0027t recognised.\n\nThe following steps will reproduce the problem when using LLVM 3.4:\n\ncat \u003c\u003cEND \u003eexample1.c\nint main() { return 0; }\nEND\ncat \u003c\u003cEND \u003eexample2.c\nvoid foo(int x) {}\nEND\n\nclang -emit-llvm -g -c example1.c -o example1.bc\nclang -emit-llvm -g -c example2.c -o example2.bc\nllvm-link-3.4 example1.bc example2.bc -o combined.bc\nclang combined.bc -o executable\n./google-breakpad/build/src/tools/linux/dump_syms/dump_syms executable\n\nWhen using LLVM bitcode linking in this way, LLVM\u0027s backend generates\npartially-merged DWARF debugging info in which some of the references\nto the \"int\" type go via \"DW_FORM_ref_addr\". Since PNaCl uses LLVM\nbitcode linking, this dump_syms failure occurs with nexes produced by\nthe PNaCl toolchain.\n\nBUG\u003d https://code.google.com/p/chromium/issues/detail?id\u003d416368\nTEST\u003d see above\nR\u003dmark@chromium.org, mcgrathr@chromium.org\n\nReview URL: https://breakpad.appspot.com/5744002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1408 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "57c3d7c9f1f86525f120337b47d6ebd586215e1e", "tree": "e1ea5f3ffccd774acfbb0f5c4622d88427c4d265", "parents": [ "97a43f9e5d6e98af3b0d8c2e63222f38fc2d262c" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Dec 02 15:31:25 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Dec 02 15:31:25 2014" }, "message": "Microdumps: support aarch64 and lib mapping from APK\n\n- Filter modules by prot flags (only +x) not extensions. It wouldn\u0027t\n otherwise catch the case of Chrome mapping the library from the\n apk (which is mapped r-x but doesn\u0027t end in .so).\n- Use compile-time detection of target arch, in order to cope with\n multilib OSes, where uname() doesn\u0027t reflect the run-time arch.\n- Add OS information and CPU arch / count.\n- Add support for aarch64.\n- Add tests and stackwalk expectations for aarch64.\n- Fix a potential overflow bug in the processor.\n- Rebaseline the tests using smaller symbols.\n- Fix microdump_writer_unittest.cc on 32-bit host.\n\nBUG\u003dchromium:410294\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1407 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "97a43f9e5d6e98af3b0d8c2e63222f38fc2d262c", "tree": "25976525bb96fc23755127dec38006dd08d46cab", "parents": [ "3ea146d00576294887aed86e25c5a5f105216a35" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Tue Nov 25 22:45:23 2014" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Tue Nov 25 22:45:23 2014" }, "message": "Surfacing the process create time in google_breakpad::ProcessState\nand updating minidump_stackwalk to show process uptime.\n\nI tested this with a minidump from Chrome and I got a result that\nis inline with what the Windows debugger is showing for that dump:\n\nminidump_stackwalk output:\n--------------------------\nProcess uptime: 601 seconds\n\nWinDBG output:\n--------------\nProcess Uptime: 0 days 0:10:01.000\n\nI didn\u0027t update the machine readable output of minidump_stackwalk\non purpose in order to avoid breaking someone that uses it.\nIt can be added later to the machine output if needed.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/7754002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1406 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "3ea146d00576294887aed86e25c5a5f105216a35", "tree": "858470a4819e4d0c50a48673a981d405ab4707e0", "parents": [ "18bd0f9a71ca98e3eecbc2fd2e85bab39276f915" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Nov 25 11:36:38 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Nov 25 11:36:38 2014" }, "message": "Introduce microdump_stackwalk comand line executable\n\nThis introduces the microdump_stackwalk binary which takes advantage\nof the MicrodumpProcessor to symbolize microdumps.\nIts operation is identical to the one of minidump_stackwalk.\nThis CL, in fact, is also refactoring most of the common bits into\nstackwalk_common.\n\nBUG\u003dchromium:410294\nR\u003dmmandlis@chromium.org\n\nReview URL: https://breakpad.appspot.com/4704002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1405 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "18bd0f9a71ca98e3eecbc2fd2e85bab39276f915", "tree": "c1d8457f5ffc7aa1b3febb4325a340575f8855fc", "parents": [ "4c5e6524c35a08cd1a107cfa59f492e89b341b94" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Nov 25 10:35:53 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Nov 25 10:35:53 2014" }, "message": "Fix microdump_writer and add unittest.\n\nThis adds some small fixes to the microdump writer and introduces\na unittest.\n\nBUG\u003dchromium:410294\nR\u003dmmandlis@chromium.org\n\nReview URL: https://breakpad.appspot.com/2814002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1404 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "4c5e6524c35a08cd1a107cfa59f492e89b341b94", "tree": "46febbd290f903ffbb7c391a6328ba4997f276fe", "parents": [ "64cdd07b885f8a6980c50ed6ee0a19ac5132db75" ], "author": { "name": "mmandlis@chromium.org", "email": "mmandlis@chromium.org", "time": "Wed Nov 19 21:33:26 2014" }, "committer": { "name": "mmandlis@chromium.org", "email": "mmandlis@chromium.org", "time": "Wed Nov 19 21:33:26 2014" }, "message": "Microdump processing implementation\n\nAccording to design document: http://goo.gl/B3wIRN\nThis is an initial implementation version, support ARM architecture only.\n\nBUG\u003dchromium:410294\nR\u003dprimiano@chromium.org\n\nReview URL: https://breakpad.appspot.com/5714003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1403 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "64cdd07b885f8a6980c50ed6ee0a19ac5132db75", "tree": "ef6bba2719848e05b442f9f103af4f1faf3b70ea", "parents": [ "3c2c398f3289fa9f8ac2d870ee4201dc3ea70f0e" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Nov 17 22:47:05 2014" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Mon Nov 17 22:47:05 2014" }, "message": "Add parameter --product to symupload.exe\n\nAdding an optional parameter --product to symupload.exe. If specified it will be passed to the symbol server as POST parameter \u0027product\u0027.\n\nAs part of this, I\u0027m also fixing:\n - Removed the .vcproj file as it can be generated from the .gyp file on demand.\n - error C4335: Mac file format detected. Fixed the line endings for omap.cc and dia_util.cc.\n - warning C4003: not enough actual parameters for macro \u0027max\u0027\n\nSymupload.exe was compiled using MSVS 2013 and DIA SDK 12.0.\n\nReview URL: https://breakpad.appspot.com/9734002/\n\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1402 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "3c2c398f3289fa9f8ac2d870ee4201dc3ea70f0e", "tree": "829810e06cea5a38ff621db6f6e7a19bfb302f82", "parents": [ "9cfd1b913b80eb96c7413c541951322939d0af05" ], "author": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Nov 05 17:40:47 2014" }, "committer": { "name": "mark@chromium.org", "email": "mark@chromium.org", "time": "Wed Nov 05 17:40:47 2014" }, "message": "Fix UMR and potential crash in Mac dump_syms.\n\nPatch by Robert Sesek \u003crsesek@chromium.org\u003e\n\nBUG\u003dhttps://code.google.com/p/google-breakpad/issues/detail?id\u003d614\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/9724002/\n\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1401 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "9cfd1b913b80eb96c7413c541951322939d0af05", "tree": "d97524e8990fa8e8673bb4b34017f8800468936a", "parents": [ "f704dbc50599728d2f3f9433a4e811a678c83f8b" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Nov 03 18:25:43 2014" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Nov 03 18:25:43 2014" }, "message": "Read dynamic symbols table even if binary contains debug info\nA\u003dWander Lairson Costa \u003cwcosta@mozilla.com\u003e. R\u003dted at https://breakpad.appspot.com/9684002/\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1400 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f704dbc50599728d2f3f9433a4e811a678c83f8b", "tree": "608f3512a22c9c8544fa450fea8a85658f0aeaae", "parents": [ "0812ec00bb29ff59cee9dc36c10814e0e6c619a4" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Nov 03 17:05:39 2014" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Mon Nov 03 17:05:39 2014" }, "message": "Fix Windows client compilation on mingw.\nA\u003dJacek Caban \u003cjacek@codeweavers.com\u003e, R\u003dted at http://breakpad.appspot.com/548002/\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1399 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "0812ec00bb29ff59cee9dc36c10814e0e6c619a4", "tree": "9c20e3247ee7dc9cfde2bb9772dafe810bc81348", "parents": [ "f37b59821ecbd69c54f3388026d2e98cd8b2fba2" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 28 16:45:14 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 28 16:45:14 2014" }, "message": "Introduce microdump writer class.\n\nMicrodumps are a very lightweight variant of minidumps. They are meant\nto dump a minimal crash report on the system log (logcat on Android),\ncontaining only the state of the crashing thread.\nThis is to deal with cases where the user has opted out from crash\nuploading but we still want to generate meaningful information on the\ndevice to pull a stacktrace for development purposes.\nConversely to conventional stack traces (e.g. the one generated by\nAndroid\u0027s debuggerd or Chromium\u0027s base::stacktrace) microdumps do NOT\nrequire unwind tables to be present in the target binary. This allows\nto save precious binary size (~1.5 MB for Chrome on Arm, ~10 MB on\narm64).\nMore information and design doc on crbug.com/410294\n\nBUG\u003dchromium:410294\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1398 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "f37b59821ecbd69c54f3388026d2e98cd8b2fba2", "tree": "19a250ec43e2fb8c7a990c0296edb70d2aaad6c3", "parents": [ "6eff9c9cbb15a431e16f98c9179858a8c1aea6cf" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Oct 24 10:58:38 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Oct 24 10:58:38 2014" }, "message": "Fix breakpad on mips and x86_64 for the NDK r10c update.\n\nThis change introduces the necessary glue typedefs to deal with the\nmismatch introduced by the latest Android NDK (w.r.t. desktop Linux):\n- [x86_64] Rename fpregs mxcr_mask -\u003e .mxcsr_mask\n- [mips] uc_mcontext.fpregs.fp_r.fp_dregs -\u003e uc_mcontext.fpreg\n- [mips] restore the forked user.h\n\nSubmitting this on behalf of fdegans@chromium.org\n\nTBR\u003dmark@chromium.org\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1397 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "6eff9c9cbb15a431e16f98c9179858a8c1aea6cf", "tree": "22ca508742634a7f82d287bcfe48f603bf9d85a0", "parents": [ "804df47d29c3604c7c1845fc4bb70c2abb17a02e" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 13:50:27 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 13:50:27 2014" }, "message": "Update breakpad to support Android NDK r10c\n\nPrior to NDK r10c, Breakpad was privately backporting these system\nheaders. This change is now unforking and removing those headers and\nusing the ones from the NDK.\nRationale:\n - They are finally available in the NDK, so there is no need to keep\n maintaining a fork (which was necessary up until recently to support\n arm64).\n - These forked headers, as they are today, are not compatible with the\n latest NDK (i.e. this change is required to roll NDK r10c).\n The forked ucontext.h, being removed by this CL, depends on some\n transitional features which are not compatible with the NDK release\n being targeted here.\n\nAfter this change, the NDK r10c is now required to build Breakpad on\nAndroid. Note that NDK releases are backwards compatible and contain all\nthe previous API levels, so this change is NOT effectively enforcing to\nbuild against any particular Android SDK.\n\nSubmitting this on behalf of fdegans@chromium.org\n\nBUG\u003dchromium:358831\nR\u003dmark@chromium.org, primiano@chromium.org, rmcilroy@chromium.org\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1396 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "804df47d29c3604c7c1845fc4bb70c2abb17a02e", "tree": "d06e13b93e4aa0cc4a39acdfe934feaf116e7a58", "parents": [ "18c60b0ba12d5b1bcc60f4e35d10feecb6e49e40" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 10:20:41 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 10:20:41 2014" }, "message": "Revert \"Remove unecessary headers following NDK r10c update.\"\n\nThis reverts r1394.\nReason for the revert: r1394 is breaking compatibility with previous\nNDK (\u003c r10c).\n\nBUG\u003dchromium:358831\nR\u003drmcilroy@chromium.org\n\nReview URL: https://breakpad.appspot.com/6754003\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1395 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "18c60b0ba12d5b1bcc60f4e35d10feecb6e49e40", "tree": "dff83940fb0790c1f29d361d68c9b5070ad3b072", "parents": [ "d307d495c30b4d48980668fc8e9ea8f9d5e0c3ef" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 08:30:28 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Tue Oct 21 08:30:28 2014" }, "message": "Remove unecessary headers following NDK r10c update.\n\nBUG\u003dchromium:358831\nR\u003dprimiano@chromium.org, rmcilroy@chromium.org\n\nReview URL: https://breakpad.appspot.com/10694002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1394 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "d307d495c30b4d48980668fc8e9ea8f9d5e0c3ef", "tree": "d06e13b93e4aa0cc4a39acdfe934feaf116e7a58", "parents": [ "945a753a70dcfcae51c24c61a28c01a658653fc0" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Fri Oct 17 17:44:09 2014" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Fri Oct 17 17:44:09 2014" }, "message": "Fixing the Mac Inspector build by adding the launch_report dependency to the breakpadUtilities dylib project after it got pulled out from Inspector.mm\n\nThis fix was provided by Thomas Schweitzer.\n\nR\u003dmark@chromium.org, mmandlis@chromium.org\n\nReview URL: https://breakpad.appspot.com/6754002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1393 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "945a753a70dcfcae51c24c61a28c01a658653fc0", "tree": "e5c733449e604ac5efaed3003ec5e505e5967f43", "parents": [ "86e45599cee2d2511fc4f9c5e1ddf5e746904baa" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Oct 17 10:58:23 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Fri Oct 17 10:58:23 2014" }, "message": "Refactor .so name detection logic in minidump/linux_dumper.\n\nThis is a refactoring of the logic which determines the\nmodule name and path for a given MappingInfo in minidump_writer.cc.\nSuch logic, which will be soon shared also with the upcoming\nmicrodump_writer.cc, is simply being moved to linux_dumper.cc,\nextracting a GetMappingEffectiveNameAndPath method.\nNo behavioral change is intended.\n\nBUG\u003dchromium:410294\nR\u003dthestig@chromium.org\n\nReview URL: https://breakpad.appspot.com/7734002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1392 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "86e45599cee2d2511fc4f9c5e1ddf5e746904baa", "tree": "ed705718c882da133fc1fd063706d6a358789fbb", "parents": [ "fa1cf76af1944b4e2e49edc630c005cb6014ceba" ], "author": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Wed Oct 15 17:15:55 2014" }, "committer": { "name": "ivanpe@chromium.org", "email": "ivanpe@chromium.org", "time": "Wed Oct 15 17:15:55 2014" }, "message": "The process uptime computation when the Windows out-of-process Crash Generation\nServer is used is done by subtracting the crashing process creation time from\nthe current time when the crash is generated:\n\n uptime \u003d now - process_creation_time\n\nThere was a bug and instead of the process creation time the code was using the\ntime when the process was registered with the Crash Generation Server.\n\nR\u003dmark@chromium.org\n\nReview URL: https://breakpad.appspot.com/1744002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1391 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "fa1cf76af1944b4e2e49edc630c005cb6014ceba", "tree": "358629c53b40895c134ce86ef98d66f2b6e322df", "parents": [ "26b381f23158ff2191e9bfff75c91677fabc636a" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Oct 09 19:34:31 2014" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Oct 09 19:34:31 2014" }, "message": "Linux multiprocess crash reporter: use pipe instead of socketpair in the client\nA\u003dJed Davis \u003cjld@mozilla.com\u003e R\u003dted at https://breakpad.appspot.com/1724002/\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1390 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "26b381f23158ff2191e9bfff75c91677fabc636a", "tree": "9c82d8bd94c6a59315cc008e59ae296dc9ff6a3f", "parents": [ "e15ba2c4d7d3b10c8c2818aa14ab66ad9a383ff6" ], "author": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Oct 09 19:34:27 2014" }, "committer": { "name": "ted.mielczarek@gmail.com", "email": "ted.mielczarek@gmail.com", "time": "Thu Oct 09 19:34:27 2014" }, "message": "Remove workaround for Linux credential-passing bug\nA\u003dJed Davis \u003cjld@mozilla.com\u003e R\u003dted at https://breakpad.appspot.com/7724002/\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1389 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "e15ba2c4d7d3b10c8c2818aa14ab66ad9a383ff6", "tree": "0554ea630f2bb466078cbc6196b2c85e52bd8cfc", "parents": [ "35189355da4b65ed5e7692f790c240a9ab347731" ], "author": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Wed Oct 01 09:51:23 2014" }, "committer": { "name": "primiano@chromium.org", "email": "primiano@chromium.org", "time": "Wed Oct 01 09:51:23 2014" }, "message": "Microdumps: refactor out common parts of minidump_writer.cc\n\nThis change is a pure refactoring of the common bits of minidump_writer.cc\nthat will be shared soon with the upcoming microdump_writer.cc.\nIn particular, this CL is extracting the following classes:\n- ThreadInfo: handles the state of the threads in the crashing process.\n- RawContextCPU: typedef for arch-specific CPU context structure.\n- UContextReader: Fills out a dump RawContextCPU structure from the\n ucontext struct provided by the kernel (arch-dependent).\n- SeccompUnwinder: cleans out the stack frames of the Seccomp sandbox\n on the supported architectures.\n- MappingInfo: handles information about mappings\n\nBUG\u003dchromium:410294\nR\u003dmmandlis@chromium.org\n\nReview URL: https://breakpad.appspot.com/4684002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1388 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" }, { "commit": "35189355da4b65ed5e7692f790c240a9ab347731", "tree": "3ffead393338c1e82e1e5074b71be85896558c35", "parents": [ "df6cb4c017c5db6e8c188b720e0f78b5f0e55f2e" ], "author": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Wed Sep 24 18:44:38 2014" }, "committer": { "name": "thestig@chromium.org", "email": "thestig@chromium.org", "time": "Wed Sep 24 18:44:38 2014" }, "message": "Fix some nits raised by Timur for r1385.\n\nR\u003divanpe@chromium.org\n\nReview URL: https://breakpad.appspot.com/1734002\n\ngit-svn-id: http://google-breakpad.googlecode.com/svn/trunk/src@1387 4c0a9323-5329-0410-9bdc-e9ce6186880e\n" } ], "next": "df6cb4c017c5db6e8c188b720e0f78b5f0e55f2e" }