summaryrefslogtreecommitdiffstats
path: root/debuggerd/debuggerd.c
Commit message (Collapse)AuthorAgeFilesLines
* Move liblog headers to system/core/include/logColin Cross2013-07-241-2/+3
| | | | | | | | | Move the liblog headers to log/ instead of cutils/ to complete the separation of libcutils and liblog. cutils/log.h still exists and includes log/log.h in order to support the many existing modules that use cutils/log.h. Change-Id: I2758c9f4aedcb809ca7ba8383d0f55041dd44345
* debuggerd: Ignore SIGPIPENick Kralevich2013-06-181-1/+3
| | | | | | | | | The system server may prematurely close the connection to /data/system/ndebugsocket if it's not interested in the data from debuggerd. If it does so, we don't want to die due to a SIGPIPE. Change-Id: Iaef1f497bcd630144e6df6a06644a3293b85b6e0
* resolved conflicts for merge of f79c0518 to jb-mr2-dev-plus-aospElliott Hughes2013-04-051-4/+10
|\ | | | | | | Change-Id: I106a2aa7ec393a68e51132bf277b22bece155a8e
| * Modify debuggerd to cope with the abort message.Elliott Hughes2013-04-041-4/+10
| | | | | | | | | | Bug: 8531731 Change-Id: I416ec1da38a8a1b0d0a582ccd7c8aaa681ed4a29
* | debuggerd now notifies the Activity Manager about native crashesChristopher Tate2013-04-011-1/+2
| | | | | | | | | | | | | | | | | | | | | | The Activity Manager sets up a permission-guarded domain socket, which debuggerd connects to when a crash happens. If this is successful, the daemon then mirrors the logged crash report to that socket, then closes it. Bug 8322568 Change-Id: Ife0c772a628ef82e8457094e511ce1edbfe57460
* | Show pid+uid in certain failuresAndy McFadden2012-12-101-4/+6
|/ | | | | | | | | | If somebody sends debuggerd bad data, it logs a complaint but doesn't give any indication of the source. Now we show the pid and uid we get from SO_PEERCRED. Bug 7704699 Change-Id: I2738eb972932cc868ad969b60e16dd0b623212a1
* [MIPS] debuggerd and libcorkscrew supportChris Dearman2012-08-101-1/+6
| | | | Change-Id: I5a241dc2e470148be0ad2c138e31f1aba5ab8812
* Enhance native stack dumps.Jeff Brown2012-06-081-530/+91
| | | | | | | | | | | | | | | | | | | | | | | | | Provides a new mechanism for dumpstate (while running as root) to request that debuggerd dump the stacks of native processes that we care about in bug reports. In this mode, the backtrace is formatted to look similar to a Dalvik backtrace. Moved the tombstone generating code into a separate file to make it easier to maintain. Fixed a bug where sometimes the stack traces would be incomplete because we were not waiting for each thread to stop after issuing PTRACE_ATTACH, only the main thread. So sometimes we were missing traces for some threads. Refactored the logging code to prevent accidentally writing data to logcat when explicitly dumping a tombstone or backtrace from the console. Only root or system server can request to dump backtraces but only root can dump tombstones. Bug: 6615693 Change-Id: Ib3edcc16f9f3a687e414e3f2d250d9500566123b
* Reduce suicidal tendenciesAndy McFadden2012-03-081-2/+12
| | | | | | | | | | | | | | | | | | Some changes to debuggerd: (1) Send a SIGSTOP to the target process before doing any of the PTRACE_ATTACH work. This causes the threads that weren't hit by the signal to stop moving, which seems to get rid of the "ptrace detach failed: No such process" problems that result in missed stack traces and debuggerd self-immolation. (2) SIGPIPE was in the list of "interesting" signals caught by debugger_signal_handler(), but debuggerd didn't recognize it, and you'd get "unexpected signal 13" complaints. It's now in the list. (3) Fixed a bit-rotted XLOG. Change-Id: I33297ea6b09ce450671c07dc25846f684afbf480
* Print the tombstone path.Jeff Brown2011-11-081-25/+55
| | | | | | | When explicitly requesting a dump, show the user the path of the tombstone file that was generated. Change-Id: I7fff7dea606872a61687ca087e99f604107b70c4
* Improve stack unwinder robustness.Jeff Brown2011-11-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Keep track of whether memory maps are readable. Use the information in try_get_word to try to avoid accidentally dereferencing an invalid pointer within the current process. (Note that I haven't ever seen that happen during normal unwinding, but it pays to be a little more careful.) Refactored try_get_word a little to make it easier to pass it the needed state for validation checks by way of a little memory_t struct. Improved how the memory map for the current process is cached. This is important because we need up to date information about readable maps. Use a 5 second cache expiration. Improved the PC -> LR fallback logic in the unwinder so we can eke out an extra frame sometimes. Fixed a bug reading ELF program headers. The phnum & phentsize fields are half-words. We were incorrectly interpreting phnum as a whole word. Used android_atomic_* operations carefully in the unwinder to prevent possible memory races between the dumper and the dumpee. This was highly unlikely (or even impossible due to the presence of other barriers along the way) but the code is clearer now about its invariants. Fixed a bug in debuggerd where the pid was being passed to have its stack dump taken instead of the tid, resulting in short stacks because ptrace couldn't read the data if pid != tid. Did a full sweep to ensure that we use pid / tid correctly everywhere. Ported old code from debuggerd to rewind the program counter back one instruction so that it points to the branch instruction itself instead of the return address. Change-Id: Icc4eb08320052975a4ae7f0f5f0ac9308a2d33d7
* Add support for explicitly dumping native stacks.Jeff Brown2011-10-251-205/+316
| | | | | | | | | | | | | | | | | | | | | | | | | This change modifies debuggerd so that it can be used to grab the native stacks of a process that has hung and not just crashed. Note that only the root user can do this (for now). adb shell debuggerd <tid> Then use logcat to find the tombstone file that was generated which will have the native stacks of all threads in the requested process. The specified thread will be shown first and will also appear in the main log. Also made some minor tweaks to libcorkscrew so that we could handle statically compiled executables in the future if we compiled the library statically. Improved the "wait_for_user_action" function to support volume down as an alternative for devices that do not have home keys. Removed a mess of gotos. Change-Id: Ic149653986b0c2f503c7f0e8b7cb1f3be7c84d1e
* Use libcorkscrew in debuggerd.Jeff Brown2011-10-221-275/+128
| | | | Change-Id: I5e3645a39d96c808f87075b49111d0262a19a0c8
* Add log summary to tombstonesAndy McFadden2011-10-181-24/+96
| | | | | | | | | | | | | | | | | | | | | When the tombstones are uploaded to APR, they're truncated at 64KB. This causes the log data, which is at the end, to be lost if the process has more than about 12 threads (which many do). This change adds the last few lines of the log right below the report for the crashing thread, where we should be guaranteed to keep it. Also, clean up trailing newlines on log messages (which end up in the tombstone), and don't print a "------- log" banner if there aren't any messages in that log file (e.g. slog). Also also, don't try to show_nearby_maps unless this is the crashing thread. Bug 5471955 Change-Id: Iaa4fd2fafbaeda2f20bb95f202177d7744a91f9d
* Append log data to tombstonesAndy McFadden2011-10-131-0/+103
| | | | | | | | | | | | | | | | | | | The Android Problem Report site shows tombstones uploaded from devices. We can see the native stack traces for every thread, but sometimes there's a very important bit of information sitting in the log, and without it we can't analyze the failure. This change modifies debuggerd so that the log contents for the crashing process are appended to the tombstone. The format matches the output of "logcat -v threadtime". Both "system" and "main" logs are included (but not interleaved -- we're not that fancy). This feature is only enabled when the "ro.debuggable" system property is set to 1 (indicating a development device). Bug 5456676 Change-Id: I3be1df59813ccf1058cec496a906f6d31fbc7b04
* Show maps near native fault addressAndy McFadden2011-10-131-7/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds some additional output to native crashes. For example, if something tried to access a bit of mmap(/dev/zero) memory that had been mprotect()ed, you might see output like this: I DEBUG : memory map around addr 4015a00c: I DEBUG : 40159000-4015a000 /system/lib/libstdc++.so I DEBUG : 4015a000-40162000 /dev/zero I DEBUG : b0001000-b0009000 /system/bin/linker The idea is to see what's in and around the fault address to make it easier to identify bus errors due to file truncation and segmentation faults caused by buffer over/underruns. No output is generated for accesses below 0x1000 (which are likely NULL pointer dereferences) or for signals that don't set si_addr. Also, suppress the fault address for signals that don't set si_addr: I DEBUG : signal 6 (SIGABRT), code 0 (?), fault addr -------- We still print "fault addr" followed by 8 characters for anything that is parsing the contents. The "address" shown for signals like SIGABRT was meaningless and possibly confusing. Bug 5358516 Change-Id: Icae8ef309ea2d89b129f68d30f96b2ca8a69cc6c
* Don't stall waiting for target to crashAndy McFadden2011-08-041-4/+28
| | | | | | | | | | | This modifies debuggerd to sleep-poll while waiting for the target process to crash, rather than block (potentially forever). Also, add/fix some error reporting. Bug 5035703 Change-Id: Id62ab79f53104927f8de684dff1a5734dbdb8390
* debuggerd can't handle debuggerd crashesAndy McFadden2011-07-291-0/+12
| | | | | | | | | | | | | | When a process receives a fatal signal, it connects to debuggerd and initiates a conversation over a socket. When the crashing process is debuggerd, the conversation stalls forever, and you stop getting native crash details. This resets the signal handlers to SIG_DFL, so that debuggerd simply crashes and gets restarted. Bug 5035703 Change-Id: Ie081d710d046f701bca7e7d8ea3e1d24766d9f61
* Revert "Debuggerd now outputs the offset of libc.so on the device as a ↵Brian Carlstrom2011-03-171-69/+0
| | | | | | | | | | | | separate item." This reverts commit c031a3b006129ca408eaade325a53a334daee3b2. Conflicts: debuggerd/debuggerd.c Change-Id: Ib37ae793bbffdb4a81837bc51171cc62b12abe7d
* debuggerd: properly unblock signal handler.David 'Digit' Turner2011-01-211-1/+13
| | | | | | | | | | | | | This change ensures that debuggered properly releases the signal handler that invoked it after the PTRACE_ATTACH. The previous code simply did a close() of the file descriptor, but for some reason, this didn't always make the read() blocking the signal handler exit. Instead, the thread would stay blocked and never fault, preventing the generation of a useful stack trace. Change-Id: I6b0579041165a710d74ec1bece113ff7b828aed4
* am 44659e90: am d3f59eab: Merge "debuggerd: IA version"Jean-Baptiste Queru2010-12-131-0/+7
|\ | | | | | | | | * commit '44659e90fe8df25c71195936eabe0cc9158c18a6': debuggerd: IA version
| * am d3f59eab: Merge "debuggerd: IA version"Jean-Baptiste Queru2010-12-131-0/+7
| |\ | | | | | | | | | | | | * commit 'd3f59eab07d102b9506978aca9541dd62dcea919': debuggerd: IA version
| | * debuggerd: IA versionBruce Beare2010-11-291-0/+7
| | | | | | | | | | | | | | | | | | Change-Id: I0c0d9c2d7e476b8d117aaf505a9480a47c0b5c05 Signed-off-by: Lei Li <lei.l.li@intel.com> Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
* | | Manual merge of 144773f9Jean-Baptiste Queru2010-12-131-206/+9
|\ \ \ | |/ / | | | | | | Change-Id: I0ac3f88ac85bbc604fdc151768da20e86318fb46
| * | am e382cc99: Merge "debuggerd: Reorganize to facilitate IA commit"Jean-Baptiste Queru2010-12-131-206/+9
| |\ \ | | |/ | | | | | | | | | * commit 'e382cc999e48b3faabea7743ec8cec303b6005ba': debuggerd: Reorganize to facilitate IA commit
| | * debuggerd: Reorganize to facilitate IA commitBruce Beare2010-11-291-206/+9
| | | | | | | | | | | | | | | Change-Id: I22dd02daf617672fc0a8ba7e396017c57f17e26e Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
* | | am 5c5ff87d: am 83c6b052: Print out the signal code along with signal number ↵Carl Shapiro2010-10-111-2/+48
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | and address. Merge commit '5c5ff87ded019537bbaf6383618ef2956aaa0407' * commit '5c5ff87ded019537bbaf6383618ef2956aaa0407': Print out the signal code along with signal number and address.
| * | am 83c6b052: Print out the signal code along with signal number and address.Carl Shapiro2010-10-101-2/+48
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | Merge commit '83c6b052918178033875e7ea54ca746cf7303f87' into gingerbread-plus-aosp * commit '83c6b052918178033875e7ea54ca746cf7303f87': Print out the signal code along with signal number and address.
| | * | Print out the signal code along with signal number and address.Carl Shapiro2010-10-081-2/+48
| | | | | | | | | | | | | | | | Change-Id: I60a8b13f706714e80b11bc517101715dfe1c73c1
* | | | Debuggerd now outputs the offset of libc.so on the device as a separate item.Hristo Bojinov2010-08-271-0/+69
|/ / / | | | | | | | | | Change-Id: I350c9ddb496a76d1ee897ae84893bf0e86abd45c
* | | am 89118032: Merge "Fix bug in debuggerd so it can successfully find the ↵Mike Dodd2010-07-161-1/+1
|\ \ \ | |/ / | | / | |/ |/| | | | | | | | | exidx section in libraries. This should fix the bug where the exception stack wasn\'t being printed past the PC." into gingerbread Merge commit '891180320f0b08758d053a8562dfcd601ef846b0' into gingerbread-plus-aosp * commit '891180320f0b08758d053a8562dfcd601ef846b0': Fix bug in debuggerd so it can successfully find the exidx section in
| * Fix bug in debuggerd so it can successfully find the exidx section inMike Dodd2010-07-141-1/+1
| | | | | | | | | | | | | | libraries. This should fix the bug where the exception stack wasn't being printed past the PC. Change-Id: Ia69ebd49606ee34e329ba43c07b325660248e8fa
* | merge from open-source masterThe Android Open Source Project2010-06-101-4/+9
|\ \ | |/ |/| | | Change-Id: I50b7bc6faa6d0abd4998cae8fc7dda1e8fa49407
| * debuggerd: Show function names in tombstone backtracesMeng Hu2010-05-241-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change enables debuggerd to provide backtraces with function names in tombstone files and log messages. It does this by reading the image file that the address is found in, and parsing the dynamic symbol table to try to extract the symbol corresponding to the given address. This works best when "-Wl,-export-dynamic" is added to the LDFLAGS of each library and executable, because this will cause all symbols to be added to the dynamic symbol table. If this flag is not present, it will still work, but it will only be able to identify functions which are part of the external API of the library/executable. Change-Id: I618baaff9ed9143b7d1a1f302224e9f21d2b0626
* | Use arch flags instead of TARGET_ARCH_VARIANT, and add support for VFP_D16Colin Cross2010-03-101-2/+10
| | | | | | | | Change-Id: I6007ff21076e92b04a17fb030472a9f8842f0315
* | Bug fix for pre-NEON platforms and enhancement for JIT debugging.Ben Cheng2010-01-281-18/+9
| | | | | | | | | | | | | | Use __ARM_NEON__ instead of __VFP_FP__ to detect the need to retrieve FP registers. Dump more code around PC and LR to facilitate JIT debugging.
* | Dump VFP registers and status word when native app crashes.Ben Cheng2009-12-171-0/+18
| | | | | | | | | | Bug: 2226399 Caveat: d0/d1 appear to be clobbered by ptrace. It will be tracked by a new bug.
* | Minor tweaks to debuggerd.Andy McFadden2009-12-011-7/+8
|/ | | | | | | | | | Changed "process has crashed" message: - say ":5039" instead of ":port" so mouse-paste of command is trivial - removed trailing spaces, which consume log buffer to little effect - improved (I hope) the short explanation of what's going on and what the HOME key does Fixed typo ("ignorning").
* Print code around PC and LR in the inline log.Ben Cheng2009-09-281-105/+95
| | | | 8 more lines should provide more crucial information in weird cases.
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-0/+852
|
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-852/+0
|
* Initial ContributionThe Android Open Source Project2008-10-211-0/+852