summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSøren Sandmann Pedersen <sandmann@daimi.au.dk>2009-02-20 07:33:24 -0500
committerSøren Sandmann Pedersen <sandmann@daimi.au.dk>2009-02-20 07:33:24 -0500
commitaf294337bdd00a27de26b73294f8d74589a0e3cc (patch)
tree2702bf886cb9bde6f454d1ae4048f8dc8d245abf /TODO
parent8577c079dc776948ccf9f11927e1aca74484bfca (diff)
Add percent signs; update TODO
Diffstat (limited to 'TODO')
-rw-r--r--TODO23
1 files changed, 17 insertions, 6 deletions
diff --git a/TODO b/TODO
index b806b89..8a2d069 100644
--- a/TODO
+++ b/TODO
@@ -30,7 +30,19 @@ Before 1.2:
considered the same symbol if they have the same parent). In fact
"has same parent" may be the correct criterion in all cases.
-* It crashes sometimes.
+ * See if we can make "In file <blah>" not be treated as a recursive function.
+ Maybe simply treat each individual address in the file as a function.
+ Or try to parse the machine code. Positions that are called are likely
+ to be functions.
+
+ - Treat identical addresses as one function
+
+ - Treat all addresses within a library that don't have children are
+ treated as one function.
+
+ This will have the effect of coalescing adjacent siblings without
+ children. Which is what you want since you can't tell them apart
+ anyway. It will never be a great experience though.
* Find out what is going on with kernel threads:
@@ -167,11 +179,6 @@ Before 1.2:
so we will have to store a list of expanded objects and keep that uptodate
as the rows expands and unexpands.
-* See if we can make "In file <blah>" not be treated as a recursive function.
- Maybe simply treat each individual address in the file as a function.
- Or try to parse the machine code. Positions that are called are likely
- to be functions.
-
* Give more sensible 'error messages'. Eg., if you get permission denied for
a file, put "Permission denied" instead of "No map"
@@ -829,6 +836,10 @@ Later:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ALREADY DONE: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+* It crashes sometimes.
+
+ I haven't seen any crashes in a long time
+
* Find out why the strings
_ZL11DisplayLineP20nsDisplayListBuilderRK6nsRectS3_R19nsLineList_iteratoriRiRK16nsDisplayListSetP12nsBlockFrame