diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2011-10-07 02:40:15 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2011-10-07 02:40:15 -0400 |
| commit | 9b4697d67d4d04ab7e41ace148fc20cb5321aa56 (patch) | |
| tree | b354f49078a672eb9e2181c9a2f194d7c71c9bde /www | |
| parent | 9826f66b57826ec68eb50dd0684a221a9690e35f (diff) | |
| download | gpsd-9b4697d67d4d04ab7e41ace148fc20cb5321aa56.tar.gz | |
Typo fixes, and fix a fossil from autotools.
Diffstat (limited to 'www')
| -rw-r--r-- | www/hacking.html.in | 14 | ||||
| -rw-r--r-- | www/troubleshooting.html | 2 |
2 files changed, 7 insertions, 9 deletions
diff --git a/www/hacking.html.in b/www/hacking.html.in index 5afb59a0..a7449e23 100644 --- a/www/hacking.html.in +++ b/www/hacking.html.in @@ -304,7 +304,7 @@ defect density of the Linux kernel itself.</p> <p>This did not happen by accident. We put a lot of effort into test tools and regression tests so we can avoid committing bad code. For committers, using those tests isn't just a good idea, it's the law -— which is to say that if make a habit of <em>not</em> using +— which is to say that if you make a habit of <em>not</em> using them when you should, your commit access <em>will</em> be yanked.</p> <p>Before shipping a patch or committing to the repository, you should @@ -448,7 +448,7 @@ to be embedding a PATH_MAX-sized buffer in the gpsd.h structure.</p> <h2 id="sizeof">Avoid use of sizeof(<int type>)!</h2> <p>It's tempting to extract parts of packets with by using a loop of the -form "<code>for(i = 0; i & len; i += sizeof(long))</code>". Don't do that; +form "<code>for(i = 0; i < len; i += sizeof(long))</code>". Don't do that; not all integer types have the same length across architectures. A long may be 4 bytes on a 32-bit machine and 8 bytes on a 64-bit. If you mean to skip 4 bytes in a packet, then say so (or use sizeof(int32_t)).</p> @@ -457,10 +457,8 @@ be 4 bytes on a 32-bit machine and 8 bytes on a 64-bit. If you mean to skip <h2 id="debugging">Debugging</h2> -<p>For debugging purposes, it may be helpful to configure with ---disable-shared. This turns off all the shared-library crud, making -it somewhat easier to use gdb. (Don't forget to set CFLAGS=-g in the -configure environment)</p> +<p><code>scons debug=yes></code> will build with the right flags to +enable symbolic debugging.</p> <p>There is a script called <code>logextract</code> in the devtools directory of the source distribution that you can use to strip clean @@ -490,8 +488,8 @@ only, suspicion should focus here.</p> <h2 id="profiling">Profiling</h2> <p>There is a timing policy flag in the WATCH command that will cause -it to that will cause it to emit timing information at the end of -every reporting cycle from the sensor.</p> +it to emit timing information at the end of every reporting cycle from +the sensor.</p> <p>The profiling code relies on the GPS repeatedly spinning through a three-phase cycle:</p> diff --git a/www/troubleshooting.html b/www/troubleshooting.html index 9dd8c790..d8070edc 100644 --- a/www/troubleshooting.html +++ b/www/troubleshooting.html @@ -162,7 +162,7 @@ argument (for example. <code>"gpsmon /dev/ttyUSB0"</code>). After a few moments to sync up, it should display a screen full of data on the device, including displaying the raw packet data streaming from it.</p> -<p>If <b>gpsmon(1)</b> reports no data at all, you mat have the device +<p>If <b>gpsmon(1)</b> reports no data at all, you ma have the device path wrong; check that using <b>dmesg(8)</b> or by whatever means you have available. If you have the right device, you may have some low-level system problem with serial or USB that you'll need to fix |