The d.start command breaks at the very first instruction of _dl_start. This behavior is more than nice, but it differs from the start command in GDB, which breaks after the prologue of the binary's main function. While I'm fine with the current implementation of d.start, it presents an issue with symbol resolution. This is because, after executing d.start(), the libc is not yet loaded, which complicates the debugging process.
The d.start command breaks at the very first instruction of _dl_start. This behavior is more than nice, but it differs from the start command in GDB, which breaks after the prologue of the binary's main function. While I'm fine with the current implementation of d.start, it presents an issue with symbol resolution. This is because, after executing d.start(), the libc is not yet loaded, which complicates the debugging process.