diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2012-10-23 11:00:59 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2012-10-23 11:00:59 -0400 |
| commit | 692416b9b348cb7f2324e24cf69b7243b422ff6d (patch) | |
| tree | 5324fb89db6dd8a53b247c13a92b42c292c6b686 /www/faq.html.in | |
| parent | 95cb1ea5e068b6f31af049a17d2620096026e7eb (diff) | |
| download | gpsd-692416b9b348cb7f2324e24cf69b7243b422ff6d.tar.gz | |
Useful bug-isolation advice.
Diffstat (limited to 'www/faq.html.in')
| -rw-r--r-- | www/faq.html.in | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/www/faq.html.in b/www/faq.html.in index 1f7ebee0..6d80ca90 100644 --- a/www/faq.html.in +++ b/www/faq.html.in @@ -304,6 +304,15 @@ core-dumped, try to use gdb or whatever your local symbolic debugger is to generate a stack trace ("bt full") of the crash, and send us that.</p> +<p>Very occasionally we have also received reports of core dumps in +gpsfake and gpson. A stack trace is also useful in those cases.</p> + +<p>A good technique in all such cases is to try to reproduce the bug +by feeding a log with the bad packet in it to gpsdecode. This utility +exercises the same packet decoders as gpsd/gpsfake/gpsmon but without +involving nearly as much other code. If you can send a test log that +crashes gpsdecode, you can expect the bug to be fixed very quickly.</p> + <h3>11. Try to determine what release introduced the bug</h3> <p>If you have upgraded from a previous version of <code>gpsd</code>, |