aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>2012-02-22 23:39:07 +0200
committerPekka Enberg <penberg@kernel.org>2012-02-23 08:33:27 +0200
commit05625ee26fbfacb146b7fc94631f56bae58affcb (patch)
tree4911b6be75bf2063a86488f73bfbcfa1b435781e
parent739b9abf517356a729a5ff30adce5ea5d57ae4e2 (diff)
downloadjato-05625ee26fbfacb146b7fc94631f56bae58affcb.tar.gz
TODO: add GDB proposal
Signed-off-by: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> Signed-off-by: Pekka Enberg <penberg@kernel.org>
-rw-r--r--TODO22
1 files changed, 22 insertions, 0 deletions
diff --git a/TODO b/TODO
index ee1120a7..eaf9bb99 100644
--- a/TODO
+++ b/TODO
@@ -328,6 +328,28 @@ Required skills::
Difficulty::
Medium
+GDB
+~~~
+Jato already hooks into GDB's JIT interface to provide basic debugging
+functionality such as backtraces and breakpoints. This could use a cleanup and
+various improvements, like the ability to display the arguments passed to a
+method. We could implement a better mangling scheme, but it's probably better
+to use the new custom debug info support in GDB 7.4. Check the
+http://sourceware.org/gdb/onlinedocs/gdb/JIT-Interface.html#JIT-Interface[GDB
+documentation] for details.
+
+Another possible improvement could be minimizing the need to disable
+optimizations.
+
+This task should be rather straightforward, but it might require digging
+through GDB to figure out possibly missing details from the documentation. It
+can be scaled according to the features one proposes to implement.
+
+Required skills::
+ C, GDB, x86(-64)
+Difficulty::
+ Medium, depends on the scope of the proposal
+
Other
-----