-
Notifications
You must be signed in to change notification settings - Fork 11
DevelopmentNotes
DWARF parser can currently find basic function symbol info based on address, but more is needed: function arguments decoding, for example.
- https://twiki.cern.ch/twiki/bin/view/Atlas/UsingPahole A library that uses DWARF debug info to analyze structures' alignment.
http://www.uplinq.com/pdf/TECH_Parallel_Computing_with_OpenCL_on_Qualcomm-based_Devices.pdf
Edda - enhanced debugger and disassembler. Uses some techniques from IDA and similar to interactively and intellectually parse any chunks of code. Advanced stack checking - you can detect what the values on the stack are most likely pointing to / representing by pressing a single button. Graphical data structures relations representation.
Drag app window and drop to other box in Network Neighborhood to run it's UI there.
- derives from BeOS-inspired app separation to server part and UI part - the server part stays on local box, while UI can migrate.
- should be relatively easy to migrate server part as well.
Some ways to achieve userfriendly interface:
- No text mode
- Data persistence
- Rich, friendly UI. Some navigational bits of Archie would be good to have from grounds up
- Component based architecture, allowing constructing system out of blocks by choosing the ones you like more.
- even connecting applications that would otherwise be command line utilies, using a graphical connection tool similar to CLAM makes it possible to create sophisticated and more flexible than unixish one-input - one-output command chaining. (a small toolbox icon on the main desktop, which opens this "tasklet" manager with a prepopulated set of ready-to-go tasklets)
A stack-based allocator sounds like a memory-effective solution. See http://www.cs.hut.fi/~tvoipio/memtutor.html