0x107000 is where the rodata section was supposed to be. Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align Name Type Addr Off Size ES Flg Lk Inf Al Here are the relevant parts: Section Headers: rodata section now? I ended up trying a couple of things and scratching my head some more, but eventually I decided to look at the binary itself and dump its content with readelf.
The sections all looked the same, the access was the same, just GRUB seemed to zero out my. I then compared the working binary from 11 months ago to the one I had now, but couldn’t find any differences for the life of me. However, Hopper revealed that the address was perfectly valid and pointed into the.
Hopper disassembler windows windows#
Finally I can use my favourite disassembler on Windows as well! /6BMkLjC0P1- Sidney Just September 12, 2018 WSL is a truly marvelous piece of engineering! Not only does it provide Windows with a good set of userland CLI tools, but I also just realized that I can run Hopper through it. I actually found out that my favourite disassembler, Hopper, runs on WSL and works quite well on Windows with a X-Server installed.
That turned out to be interesting, instead of printing ‘Hello’ it printed ‘ìe°├UëÕ]Ús UëÕâýj’. rodata section (although separate from the strings). I tried allocating a buffer on the stack and putting a short string in there, unfortunately Clang was smart enough to detect what it was and also put it into the. Just to make sure I also put a breakpoint into the first instruction run after the kernel is loaded and the null byte was still there. There is no virtual memory, everything is essentially as GRUB had set it up. That didn’t make any sense though, it was early in the boot process and firedrake doesn’t do any relocation at that point yet. When looking at the memory at the address, I found a single lone null byte which explained why there was no output, kputs() figured that it was passed a empty string.
I put a breakpoint in the kputs() function and checked it’s input: 0x0010718c. That’s strange, I thought, messed with a couple of things and also stashed all my git changes but no avail No more output via the UART.Īlright, debugger time, QEMU is nice enough to provide a gdbserver that can be connected to. Then I compiled firedrake from scratch and it stopped working, or rather, it stopped producing output via the UART. I fired up the last compiled version I had, just to remind myself of where I had left things, and I QEMU was happy to dump my debug printf()’s via the virtual UART into stdout. So I set up WSL, installed all necessary dependencies and opened firedrake. 11 months ago was the last time I touched firedrake, and last weekend the urge to mess with it caught me again.
0 kommentar(er)
