| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 5016 | Kartik Agaram | 2019-03-22 | 1 | -0/+8 |
| | | |||||
| * | 4987 - support `browse_trace` tool in SubX | Kartik Agaram | 2019-02-25 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | I've extracted it into a separate binary, independent of my Mu prototype. I also cleaned up my tracing layer to be a little nicer. Major improvements: - Realized that incremental tracing really ought to be the default. And to minimize printing traces to screen. - Finally figured out how to combine layers and call stack frames in a single dimension of depth. The answer: optimize for the experience of `browse_trace`. Instructions occupy a range of depths based on their call stack frame, and minor details of an instruction lie one level deeper in each case. Other than that, I spent some time adjusting levels everywhere to make `browse_trace` useful. | ||||
| * | 4964 | Kartik Agaram | 2019-02-14 | 1 | -1/+1 |
| | | |||||
| * | 4936 | Kartik Agaram | 2019-01-18 | 1 | -1/+1 |
| | | |||||
| * | 4922 | Kartik Agaram | 2019-01-11 | 1 | -6/+6 |
| | | |||||
| * | 4921 | Kartik Agaram | 2019-01-11 | 1 | -2/+2 |
| | | |||||
| * | 4915 | Kartik Agaram | 2019-01-08 | 1 | -0/+30 |
| | | | | | | | In the process of building next-token I finally added some support for a debugging situation I've found myself in a couple of times: wondering "what changed this memory location"? | ||||
| * | 4678 | Kartik Agaram | 2018-10-10 | 1 | -0/+25 |
| A debugging aid: 'subx --map translate' dumps a mapping from functions to addresses to a file called "map", and 'subx --map run' loads the mapping in "map", augmenting debug traces. Let's see how much this helps. Debugging machine code has been pretty painful lately. | |||||