forked from qt-creator/qt-creator
Debugger: Put some restrictions on byte array dumper
This makes 100M a hard limit, reducing the likelihood that an uninitialized byte array will look valid. Change-Id: I51dc5f39e0c7327faa8c1d0640934a6074d8c559 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This commit is contained in:
@@ -58,6 +58,7 @@ def qform__QByteArray():
|
||||
|
||||
def qdump__QByteArray(d, value):
|
||||
data, size, alloc = d.byteArrayData(value)
|
||||
d.check(0 <= size and size <= alloc and alloc <= 1000 * 1000 * 100)
|
||||
d.putNumChild(size)
|
||||
elided, p = d.encodeByteArrayHelper(d.extractPointer(value), d.displayStringLimit)
|
||||
displayFormat = d.currentItemFormat()
|
||||
@@ -78,6 +79,7 @@ def qdump__QByteArray(d, value):
|
||||
|
||||
def qdump__QByteArrayData(d, value):
|
||||
data, size, alloc = d.byteArrayDataHelper(d.addressOf(value))
|
||||
d.check(0 <= size and size <= alloc and alloc <= 1000 * 1000 * 100)
|
||||
d.putValue(d.readMemory(data, size), Hex2EncodedLatin1)
|
||||
d.putNumChild(1)
|
||||
if d.isExpanded():
|
||||
|
||||
Reference in New Issue
Block a user