| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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. | |||||