Changes between Version 1 and Version 2 of Ticket #9858, comment 28
- Timestamp:
- Nov 13, 2014, 1:12:11 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #9858, comment 28
v1 v2 14 14 }}} 15 15 16 Recompile cdda with that memset() in; the change is harmless in itself, in that it will not turn correct code into incorrect code: it is legit to write whatever one wants in a const char*buffer before returning it to the system. The interest lies in the fact that the written string sometimes does end up in the KDL message.. (address 0x7a7a7a7a, ascii for "zzzz"). ! It'd be interesting if that is true in your testing as well as in mine.16 Recompile cdda with that memset() in; the change is harmless in itself, in that it will not turn correct code into incorrect code: it is legit to write whatever one wants in a ''char*'' buffer before returning it to the system. The interest lies in the fact that the written string sometimes does end up in the KDL message.. (address 0x7a7a7a7a, ascii for "zzzz"). ! It'd be interesting if that is true in your testing as well as in mine. 17 17 18 18 Anyway that suggestion is based on the assumption that knowing which variable [ 's contents] contains the corrupting buffer, is useful in identifying the code that is guilty of copying that contents into a wild place. Maybe one does not lead to the other and that assumption is wrong though..