Recent changes to Home

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Fri, 08 Apr 2016 23:19:07 -0000

--- v9
+++ v10
@@ -49,11 +49,7 @@
 0x7fffffffe340 0x000000000040050c testf
 0x7fffffffe360 0x000000000040052d main
 ~~~~
-
-Limitations
----
-
-Current Stackcheck version doesn't handle multithreading, yet. Multithreading support is in our roadmap. 
+

 [[members limit=20]]
 [[download_button]]

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Fri, 08 Apr 2016 22:39:38 -0000

--- v8
+++ v9
@@ -22,6 +22,8 @@
 1. Recompile the program (binary under test) to include debugging information (gcc –g);
 2. Locate the preferred version of gdb and use its path; “gdb” is used by default;
 3. Run stackcheck.py;
+
+Stackcheck points to the code line that goes **after** the one that overwrote the stack.

 Test
 ---

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Fri, 08 Apr 2016 03:36:13 -0000

--- v7
+++ v8
@@ -12,7 +12,7 @@
 Synopsis
 ---

-`stackcheck.py [-g <path_to_gdb>] path_to_binary_under_test`
+`stackcheck.py [-g <path_to_gdb>] path_to_binary_under_test [arg1] ...`

 Description
 ---

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Wed, 06 Apr 2016 00:10:41 -0000

--- v6
+++ v7
@@ -2,7 +2,7 @@

 Quercitools has just one tool for now - stackcheck.py. It helps in troubleshooting of stack overruns. Such defects destroy stack contents and locating the source of the problem is not easy. This is where stackcheck.py comes to help. It runs a program under test by gdb and protects some parts of the stack. If the program overwrites such parts stackcheck.py stops the program and point to the offending line of code.

-Stackcheck uses hardware checkpoints for speed and doesn't step through the program. It is designed to troubleshoot production software, but as long as gdb is involved there is some performance penalty.
+Stackcheck uses hardware checkpoints for speed and doesn't step through the program, but as long as gdb is involved there is some performance penalty.

 Installation
 ---

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Wed, 06 Apr 2016 00:06:20 -0000

--- v5
+++ v6
@@ -1,6 +1,8 @@
 # Quercitools

 Quercitools has just one tool for now - stackcheck.py. It helps in troubleshooting of stack overruns. Such defects destroy stack contents and locating the source of the problem is not easy. This is where stackcheck.py comes to help. It runs a program under test by gdb and protects some parts of the stack. If the program overwrites such parts stackcheck.py stops the program and point to the offending line of code.
+
+Stackcheck uses hardware checkpoints for speed and doesn't step through the program. It is designed to troubleshoot production software, but as long as gdb is involved there is some performance penalty.

 Installation
 ---

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Tue, 05 Apr 2016 22:09:28 -0000

--- v4
+++ v5
@@ -46,6 +46,10 @@
 0x7fffffffe360 0x000000000040052d main
 ~~~~

+Limitations
+---
+
+Current Stackcheck version doesn't handle multithreading, yet. Multithreading support is in our roadmap. 

 [[members limit=20]]
 [[download_button]]

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Tue, 05 Apr 2016 21:54:47 -0000

--- v3
+++ v4
@@ -21,6 +21,31 @@
 2. Locate the preferred version of gdb and use its path; “gdb” is used by default;
 3. Run stackcheck.py;

+Test
+---
+
+Included is test program test4.c that overwrites its stack. Test run:
+
+
+~~~~
+$ cc -o test4 -g  test4.c
+$ ./stackcheck.py -g /u/slozovsky/gdb/bin/gdb test4
+
+=== Stack Overrun ===
+Overwritten address: *0x7fffffffe360
+Frame:
+{'addr': '0x000000000040051a',
+ 'args': [{'name': 'a', 'value': '0x7fffffffe358'}],
+ 'file': 'test4.c',
+ 'fullname': '/usr/home/nfs/slozovsky/Development/gdb1/test4.c',
+ 'func': 'testf',
+ 'line': '12'}
+
+Back trace (rbp, function address, function name):
+0x7fffffffe340 0x000000000040050c testf
+0x7fffffffe360 0x000000000040052d main
+~~~~
+

 [[members limit=20]]
 [[download_button]]

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Tue, 05 Apr 2016 21:34:09 -0000

--- v2
+++ v3
@@ -10,7 +10,7 @@
 Synopsis
 ---

-stackcheck.py [-g <path_to_gdb>] path_to_binary_under_test
+`stackcheck.py [-g <path_to_gdb>] path_to_binary_under_test`

 Description
 ---

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Tue, 05 Apr 2016 21:33:21 -0000

--- v1
+++ v2
@@ -1,8 +1,26 @@
-Welcome to your wiki!
+# Quercitools

-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+Quercitools has just one tool for now - stackcheck.py. It helps in troubleshooting of stack overruns. Such defects destroy stack contents and locating the source of the problem is not easy. This is where stackcheck.py comes to help. It runs a program under test by gdb and protects some parts of the stack. If the program overwrites such parts stackcheck.py stops the program and point to the offending line of code.

-The wiki uses [Markdown](/p/quercitools/wiki/markdown_syntax/) syntax.
+Installation
+---
+
+Unpack the distribution tar file into some directory. The latest version of gdb is recommended.
+
+Synopsis
+---
+
+stackcheck.py [-g <path_to_gdb>] path_to_binary_under_test
+
+Description
+---
+
+If the program corrupts its stack:
+
+1. Recompile the program (binary under test) to include debugging information (gcc –g);
+2. Locate the preferred version of gdb and use its path; “gdb” is used by default;
+3. Run stackcheck.py;
+

 [[members limit=20]]
 [[download_button]]

Home modified by Sergiy Lozovsky

Sergiy Lozovsky — Tue, 05 Apr 2016 02:11:07 -0000

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Members:

Sergiy Lozovsky (admin)