From d2fc36701fdc92509bd8fb214a0dccf8e28dd2ea Mon Sep 17 00:00:00 2001 From: Chiller Dragon Date: Sun, 8 Mar 2020 14:09:55 +0100 Subject: [PATCH] Happy new year 2020 (#718) --- README.md | 2 +- docs/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e0531ba39..160876bb3 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ It has a boatload of features, see [FEATURES.md](FEATURES.md). ## Why? -Vanilla GDB is terrible to use for reverse engineering and exploit development. Typing `x/g30x $esp` is not fun, and does not confer much information. The year is 2019 and GDB still lacks a hexdump command! GDB's syntax is arcane and difficult to approach. Windbg users are completely lost when they occasionally need to bump into GDB. +Vanilla GDB is terrible to use for reverse engineering and exploit development. Typing `x/g30x $esp` is not fun, and does not confer much information. The year is 2020 and GDB still lacks a hexdump command! GDB's syntax is arcane and difficult to approach. Windbg users are completely lost when they occasionally need to bump into GDB. ## What? diff --git a/docs/index.md b/docs/index.md index f5f3bd947..723c6be73 100644 --- a/docs/index.md +++ b/docs/index.md @@ -6,7 +6,7 @@ It has a boatload of features, see [FEATURES.md](https://github.com/pwndbg/pwndb ## Why? -Vanilla GDB is terrible to use for reverse engineering and exploit development. Typing `x/g30x $esp` is not fun, and does not confer much information. The year is 2019 and GDB still lacks a hexdump command! GDB's syntax is arcane and difficult to approach. Windbg users are completely lost when they occasionally need to bump into GDB. +Vanilla GDB is terrible to use for reverse engineering and exploit development. Typing `x/g30x $esp` is not fun, and does not confer much information. The year is 2020 and GDB still lacks a hexdump command! GDB's syntax is arcane and difficult to approach. Windbg users are completely lost when they occasionally need to bump into GDB. ## What?