[HN Gopher] MIPS stacktrace: an unexpected journey
       ___________________________________________________________________
        
       MIPS stacktrace: an unexpected journey
        
       Author : smeso
       Score  : 15 points
       Date   : 2024-04-08 09:26 UTC (1 days ago)
        
 (HTM) web link (smeso.it)
 (TXT) w3m dump (smeso.it)
        
       | fweimer wrote:
       | I wonder if the toolchain generated unwind tables. It's not
       | unusual to disable them in embedded contexts. Without them, the
       | DWARF-based libgcc unwinder won't worm, obviously.
        
       | evmar wrote:
       | I have been working on an x86 emulator[1] so I have x86 on the
       | mind. As I read the post I was thinking to myself "there's no way
       | you can iterate the instruction stream without a massive amount
       | of effort to parse through all different instruction types"...
       | and then remembered MIPS has constant-sized instructions. So
       | nice!
       | 
       | But also I glanced at some MIPS docs and it seems there there
       | could be additional instructions that modify these registers as
       | outputs, which the code doesn't address. Maybe they just don't
       | occur in practice?
       | 
       | [1] https://github.com/evmar/retrowin32
        
       ___________________________________________________________________
       (page generated 2024-04-09 23:01 UTC)