diff options
| author | Mukund Sivaraman <muks@banu.com> | 2009-09-27 19:09:51 +0530 |
|---|---|---|
| committer | Mukund Sivaraman <muks@banu.com> | 2009-09-27 19:09:51 +0530 |
| commit | 44e32f15d796dd6d046e78c1bd7e0aff0c076269 (patch) | |
| tree | f802ecc96cc928b634ca3dc2ff3c6dbac45f62ea | |
| parent | bf38e2e68bfed900a72cba972bfe5b37561fb492 (diff) | |
| download | tinyproxy-44e32f15d796dd6d046e78c1bd7e0aff0c076269.tar.gz tinyproxy-44e32f15d796dd6d046e78c1bd7e0aff0c076269.zip | |
Remove section on debugging from README
| -rw-r--r-- | README | 21 |
1 files changed, 0 insertions, 21 deletions
@@ -69,27 +69,6 @@ please visit: for more information on how to subscribe and post messages to the lists. -Please recompile Tinyproxy with full debug support (--enable-debug) and -include a copy of the log file, and any assert errors reported by -Tinyproxy. Note that Tinyproxy will output memory statistics to -standard error if compiled with debugging support so you might want to -redirect the output to a file for later examination. Also, if you feel -up to it, try running Tinyproxy under your debugger and report the error -your received and a context listing of the location. Under gdb you -would run Tinyproxy like so: - - gdb tinyproxy - - (gdb) run -c location_of_tinyproxy_conf -d 2>/dev/null - -Now access the port Tinyproxy is on until you receive a break in the -gdb. You can now type: - - (gbd) l - -to produce a context listing of the location of the error. Send a -copy to the authors. - Contributing ------------ |