| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fred Wright <fhgwright> writes:
While trying the regression tests on a MacBook (PowerPC), I ran across
some failures in the JSON unit test. Although this is ostensibly an
endian issue, it turns out that the code for parsing satellite view
data is actually incorrect for all processors, albeit more so for
big-endian processors.
The problem is that the three "integer" fields in struct satellite_t
are defined as shorts, but parsed as ints by the JSON parser. On a
big-endian processor, this causes the values to be misaddressed and
hence have incorrect values, but even on a little-endian processor
this is incorrect since it's storing four-byte values into two-byte
fields. The unit tests don't catch this aspect, since the fields are
favorably ordered such that the clobbered fields are clobbered before
being written pseudo-correctly.
I was able to demonstrate the "buffer overflow" misbehavior by
modifying the test data for the last satellite to provide the fields
in the reverse order from their order in the structure.
The simple fix for this would be just to change the shorts to ints in
the definition of struct satellite_t. On most processors, this doesn't
even cost any memory, since the presence of the double forces
eight-bye alignment, so the padded structure is 24 bytes regardless of
whether the three fields in question are shorts or ints. However,
there might be some processors with less strict alignment requirements
where using shorts would actually be helpful.
With the existing layout, the only possible fix is to add support for
shorts to the JSON parser, and adjust the satellite-view parsing
accordingly. The attached patch does that, as well as adding u_short
support for completeness (though it's not currently used). It also
provides the aforementioned change in the test data, in keeping with
the philosophy of "create a test for what just failed, so it doesn't
happen again".
Note that using shorts for these fields would be more effective if the
"used" field were also reduced to a short, instead of inheriting "int"
from "bool". That would shrink the structure to 16 bytes. It could be
further reduced to 12 bytes by using a float instead of a double for
the "ss" field (and even a float is gross overkill for this
purpose). This could all be more significant when MAXCHANNELS needs to
be increased (again) to accommodate the deployment of the newer
GNSSes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proximate cause was that we've been seing emission of error
messages that were randomly and disturbingly variable across different
environments - notably Raspbian and Gentoo splint gave nontrivially
different results than Ubuntu 14.10 splint. And this was *not* due to
Ubuntu patches! A pristine splint built from the 3.1.2 tarball on
Ubuntu didn't match the Raspbian and Gentoo results either.
But this has been coming for a while. Easy access to more modern
static analyzers such as coverity, scan-build and cppcheck has been
decreasing the utility of splint, which is unmaintained and somewhat
buggy and not easy to use.
Only file not cleaned is ppsthread.c, because Gary has been working
on it during this cleanup.
All regression tests pass. PPS observed live on GR601-W.
|
|
|
|
| |
gpsd.c is now splint clean on raspbian. YMMV
|
|
|
|
|
|
| |
Now supported: JSON arrays with int, unit, bool, and real elements.
All regressiion tests pass.
|
| |
|
|
|
|
| |
...and it's used for the new dependent _text attributes.
|
| |
|
|
|
|
|
|
|
| |
This will allow the parsing long hexdump (data fields) in the AIS code.
The longest JSON string I saw so far was 389 characters long.
scons check passed.
|
| |
|
|
|
|
|
| |
Should never happen, but having the bailout logic in plavce creates static
invariants that should banish a bunch of Coverity warnings.
|
| |
|
|
|
|
|
|
|
| |
Sigh, no other way to get DEVICELIST to recignize both new and old
timestamps.
All regression tests pass.
|
|
|
|
| |
Fixes Berlios tracker bug #17379: problem with different locale.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All regression tests pass.
Note from esr: this feature cannot be announced yert, as it requires
documentation in the INSTALL file.
1. What the target environments are (Linux? Windows? Both)
2. All build prerequisites (C++ compiler? Qt library? Other libraries?)
3. What the new files libQgpsmm_global.h and libQgpsmm.pro are for,
and how the are used.
We also need to know how to regression-test this code under Linux so
we can verify that it's not broken as the client library evolves.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
| |
That is, if the CLIENTDEBUG_ENABLE feature switch is on. All
regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also add a unit test for this.
|
|
|
|
|
| |
Make gpsctl work with new protocol (only the device ID function is
tested at this point).
|
|
|
|
| |
so that string lengths won't step on offsets.
|
|
|
|
| |
Too much complexity for too little gain.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Add JSON unit test to default test sequence.
|
|
|
|
|
| |
...at least for the simplest case ?WATCH={"TPV":true}. More testing
will follow.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|