Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1426)

Unified Diff: sky/HACKING.md

Issue 1196223004: Add more details to how to debug with gdb. (Closed) Base URL: https://github.com/domokit/mojo.git@master
Patch Set: Created 5 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: sky/HACKING.md
diff --git a/sky/HACKING.md b/sky/HACKING.md
index de70d7d47d0cc88d6feededcee7e226921003bf1..90b45578d72f3a02b199d5c1422e416a1dbb21c9 100644
--- a/sky/HACKING.md
+++ b/sky/HACKING.md
@@ -66,7 +66,7 @@ Debugging Sky
This document aims to explain how to debug Sky itself.
-=== C++
+### C++
Launch a debug Sky build on Linux as follows (where `app.dart` is the
test you are running and trying to debug):
@@ -76,6 +76,13 @@ mojodb start --gdb out/Debug app.dart
mojodb gdb_attach
```
-=== Dart
+Once gdb has loaded, hit `c` to start the app. The linux simulator
+will load (slowly), after spawning many threads. When your app
+crashes, it will pause in the debugger. At that point, regular gdb
+commands will work: `n` to step over the current statement, `s` to
+step into the current statement, `f` to step out of the current block,
+`c` to continue until the next breakpoint or exception.
+
+### Dart
Use Observatory.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698