| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-limits-rolling.patch | Use limits header in RollingMean.cc | Jose Luis Rivero <jrivero@osrfoundation.org> | no | 2020-11-25 | ||
| 0002_use_system_gtest.patch | Use system packaged gtest | "gladk@debian.org" <gladk@debian.org> | no | 2020-01-10 | ||
| 0002-Disable-symbol-test.patch | Disable symbol test | Jochen Sprickerhof <jspricke@debian.org> | no | 2020-04-13 | ||
| 0004-Check-expected-string-in-architectures-that-fail-wit.patch | Check expected string in architectures that fail with negative zero due to optimizations | Jose Luis Rivero <jrivero@osrfoundation.org> | no | 2020-09-08 | ||
| 0005-Properly-handle-stream-errors-when-reading-math-obje.patch | Properly handle stream errors when reading math objects Many classes use temporary variables in operator>> to read data from the stream. However, if stream operations fail, the variables will not be modified, and the temporary variables, which are POD data types, remain uninitialized. Often, but not always, this happens to be zero, which is probably why this bug remained undetected for so long. This is ultimately the reason why the sdformat Utils_TEST sometimes fails with an empty pose string: the empty string causes the uninitialized values to propagate to the Pose, while the unit test clearly expects the default value. This PR modifies the >> operators such that an invalid input will not change the underlying object at all. |
=?utf-8?q?Timo_R=C3=B6hling?= <timo@gaussglocke.de> | yes | 2020-11-26 |