commit | 7510e4aac5afa0d796e60046eecfe48966e46d64 | [log] [tgz] |
---|---|---|
author | Magnus Jedvert <magjed@webrtc.org> | Sun Jan 20 11:46:32 2019 +0100 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jan 21 15:18:56 2019 +0000 |
tree | 69bff4fe5f7cfc910067df6d3510a3999c1ed311 | |
parent | dfc7d639781cc800ada1fd04847429e5806812d1 [diff] |
Reland "Android: Add helper methods for printing native stack traces" This is a reland of dc32cc00e80972223767be339f9318b803f4a2ae Relanding because this CL was not the culprit for the Chrome bot. (This code shouldn't even be executed in Chrome). Original change's description: > Android: Add helper methods for printing native stack traces > > This CL adds utility functions to unwind the stack for a given thread on > Android ARM devices. This works on top of unwind.h and unwinds native > (C++) stack traces only. Unwinding a thread from another thread is done > by overriding the signal handler with a custom function and then > interrupting the specific thread. > > Bug: webrtc:10168 > Change-Id: If5adffd3a6bb57bf502168743e09a7eefc292bf3 > Reviewed-on: https://webrtc-review.googlesource.com/c/118141 > Commit-Queue: Magnus Jedvert <magjed@webrtc.org> > Reviewed-by: Tommi <tommi@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#26328} TBR=tommi Bug: webrtc:10168 Change-Id: I4c33c2c147cf10c0172c98a55d32dd35a08517c8 Reviewed-on: https://webrtc-review.googlesource.com/c/118704 Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Commit-Queue: Magnus Jedvert <magjed@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26341}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.