diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2010-05-20 16:32:42 +0200 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2010-05-20 16:32:42 +0200 |
| commit | 035133028d5be518b51de7dc71638319e1c54ecf (patch) | |
| tree | bbfa4dd247c097007ab890b3266144ef4397681c | |
| parent | 128cf1b5e5738597288dd0120ced63a0334d4698 (diff) | |
| download | rsyslog-035133028d5be518b51de7dc71638319e1c54ecf.tar.gz rsyslog-035133028d5be518b51de7dc71638319e1c54ecf.tar.xz rsyslog-035133028d5be518b51de7dc71638319e1c54ecf.zip | |
fixed typo in doc
| -rw-r--r-- | doc/troubleshoot.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/troubleshoot.html b/doc/troubleshoot.html index 16b2754b..0f0c7fca 100644 --- a/doc/troubleshoot.html +++ b/doc/troubleshoot.html @@ -113,7 +113,7 @@ the development versions). <p>Active support from the user base is very important to help us track down those things. Most often, serious problems are the result of some memory misadressing. During development, we routinely use valgrind, a very well and capable memory debugger. This helps us to create -pretty clean code. But valgrind can not detect anything, most importantly not code pathes +pretty clean code. But valgrind can not detect everything, most importantly not code pathes that are never executed. So of most use for us is information about aborts and abort locations. <p>Unforutnately, faults rooted in adressing errors typically show up only later, so the actual abort location is in an unrelated spot. To help track down the original spot, |