diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2021-05-07 15:21:48 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2021-05-07 15:28:17 -0700 |
| commit | 540fd664738dfb45d4373497c4a316828e9b1a33 (patch) | |
| tree | e1cc29cb658117e73fbc5e2aa6a3e0c6bff18225 /mu_instructions | |
| parent | d3f17627d88f7a128ae398cca9f1b7fce2a7575e (diff) | |
| download | mu-540fd664738dfb45d4373497c4a316828e9b1a33.tar.gz | |
a little bit more information when lookup fails
Basically this should never, ever happen until I start reclaiming heap memory. I believe the only reason it happens is unprotected writes to address 0 or thereabouts.
Diffstat (limited to 'mu_instructions')
0 files changed, 0 insertions, 0 deletions