- 50comments
- 133comments
- 28comments
- 64comments
- 56comments
- 5comments
- 43comments
- —discuss
- 151comments
- 618comments
- —discuss
- 301comments
- 44comments
- 26comments
- 246comments
- 96comments
- 173comments
- 78comments
- 10comments
- 238comments
- 51comments
- 142comments
- —discuss
- 163comments
- 18comments
- 27comments
- 70comments
- 29comments
- 47comments
- —discuss
I'm not sure this is correct. If you have a new enough version of GDB, I think you can reverse-step and reverse-next.
You're right, gdb has had some reverse debugging support since version 7.0 released in 2009.
https://www.gnu.org/software/gdb/news/reversible.html
GDB's built-in record and replay target is too slow to be very useful. It laboriously breaks on every instruction, decodes it, and records its effects; rr is much, much smarter. With GDB you might record execution for a short a minute or two, but with rr you can record everything, all the time. It's fast enough that you could record your every-day browsing sessions just in case you encounter a bug.
On the other hand, you are technically correct.