| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Flan -> Froyo | Andy McFadden | 2010-02-16 | 1 | -2/+2 |
| | | |||||
| * | Don't assume debugger wants all exceptions. | Andy McFadden | 2009-12-11 | 1 | -6/+0 |
| | | | | | | | | | | | | | | The JDWP implementation in the VM keeps a list of the objects that the debugger knows about, and prevents the GC from collecting them (which isn't strictly necessary, but it's a whole lot easier than doing it right). Because of the way it's implemented, it actually ended up keeping track of all thrown exceptions, even if the debugger wasn't interested in hearing about them. With this change we now do a "late" registration of the exception object, preventing exception-happy code from filling memory when the debugger is attached. | ||||
| * | Update docs for debugger change. | Andy McFadden | 2009-11-30 | 1 | -8/+7 |
| | | | | | Update notes re: breakpoint implementation (changed Oct 28, 96516932). | ||||
| * | Update notes on JDWP debugger support. | Andy McFadden | 2009-07-06 | 1 | -6/+11 |
| | | | | | | | | | In particular: - The app framework uses ro.debuggable, not ro.secure, to decide whether or not debuggers are globally allowed. - If you have a debugger attached, Thread objects may not be collected. | ||||
| * | Updated the "weird stuff you might see" section. | Andy McFadden | 2009-04-24 | 1 | -0/+34 |
| | | |||||
| * | auto import from //depot/cupcake/@135843 | The Android Open Source Project | 2009-03-03 | 1 | -0/+211 |
| | | |||||
| * | auto import from //depot/cupcake/@132589 | The Android Open Source Project | 2009-03-03 | 1 | -211/+0 |
| | | |||||
| * | auto import from //depot/cupcake/@137055 | The Android Open Source Project | 2009-03-02 | 1 | -0/+211 |
