From 73cf54a3db8cdfb9e1d057394056aed2cd5d99ff Mon Sep 17 00:00:00 2001 From: Robin Nicholson Date: Fri, 16 Mar 2018 23:57:26 +0100 Subject: [PATCH] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d6affa9..a50558e 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,6 @@ Call graph after change(the code does not change, but the runtime execution does ![](https://github.com/mollismerx/elfspy/blob/master/images/spy%20after.png) -This technique relies on code being compiled as [position independent code](https://en.wikipedia.org/wiki/Position-independent_code) and uses the Executable and Linking Format([ELF](https://refspecs.linuxfoundation.org/elf/elf.pdf)) information found in the executable and its shared libraries to find the global offset table entriesi and modify them. +This technique relies on code being compiled as [position independent code](https://en.wikipedia.org/wiki/Position-independent_code) and uses the Executable and Linking Format([ELF](https://refspecs.linuxfoundation.org/elf/elf.pdf)) information found in the executable and its shared libraries to find the global offset table entries and modify them. To see how ELFspy can be used start by reading this [example](https://github.com/mollismerx/elfspy/wiki/Example-01:-Spying-on-code)