al13n

4 ms·

1. 1.▲
   by al13n 1y ago

   Weird. Maybe the binary is just built without debug info? Does the list of binaries at the top right say whether debug info was loaded? Are file names and line numbers shown, e.g. in stack trace? Press 'o' in the code window to se
2. 2.▲
   by al13n 1y ago

   I don't have all details, but seems like lots of work: * Mach APIs instead of ptrace (probably a lot of changes). * Mach-O instead of ELF. * Some other APIs instead of /proc/<pid>/{maps,stat,...} * Probably arm in
3. 3.▲
   by al13n 1y ago

   Here's an overly long reply, sorry :) For custom pretty-printers, the long-term plan is to make the watch expression language rich enough that you can just write one-liners in the watches window to pretty-print your struct. E.g. `for e
4. 4.▲
   by al13n 1y ago

   In this post's case, I went with TUI over GUI to make it work over SSH, which is how I use it most of the time.
5. 5.▲
   by al13n 1y ago

   Fun fact: gdb tui was the last straw that made me start working on nnd. I tried it for the first time, and it was taking 2 seconds to respond to every input, and that made me so angry I started researching how to make a debugger :)
6. 6.▲
   by al13n 1y ago

   Hi, author here :) Didn't expect it to be posted, readme maybe doesn't have enough context. It just says "Essential features are there". What are those? Most of what I've ever used in any debugger: * Showing code, d