Skip to content

Commit f50dd84

Browse files
committed
CPP: Rename good and bad example files.
1 parent d198b56 commit f50dd84

3 files changed

Lines changed: 2 additions & 2 deletions

File tree

cpp/ql/src/Likely Bugs/Memory Management/NtohlArrayBad.cpp renamed to cpp/ql/src/Likely Bugs/Memory Management/NtohlArrayNoBound-bad.cpp

File renamed without changes.

cpp/ql/src/Likely Bugs/Memory Management/NtohlArrayGood.cpp renamed to cpp/ql/src/Likely Bugs/Memory Management/NtohlArrayNoBound-good.cpp

File renamed without changes.

cpp/ql/src/Likely Bugs/Memory Management/NtohlArrayNoBound.qhelp

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ it to host byte order. The data is then used as an index in an array access expr
3131
there is no validation that the data returned by <code>ntohl</code> is within the bounds of the array,
3232
which could lead to reading outside the bounds of the buffer.
3333
</p>
34-
<sample src="NtohlArrayBad.cpp" />
34+
<sample src="NtohlArrayNoBound-bad.cpp" />
3535
<p>In the corrected example, the returned data is validated against the known size of the buffer,
3636
before being used as an array index.</p>
37-
<sample src="NtohlArrayGood.cpp" />
37+
<sample src="NtohlArrayNoBound-good.cpp" />
3838
</example>
3939

4040
<references>

0 commit comments

Comments
 (0)