Happy new year 2020 (#718)

This commit is contained in:
Chiller Dragon 2020-03-08 14:09:55 +01:00 committed by GitHub
parent f2c0efc10d
commit d2fc36701f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -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?

View File

@ -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?