3 Commits (cf482d702bbc5eeef12bbfdaefd2710e727dece3)

Author	SHA1	Message	Date
Lars Knoll	50661a9558	Change QByteArray to handle large arrays ... Use qsizetype throughout. Change-Id: I787af7fcfa17e1be87decb64c41c609cc24be117 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Lars Knoll <lars.knoll@qt.io> Reviewed-by: Oliver Wolff <oliver.wolff@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>	2020-08-27 18:58:20 +02:00
Thiago Macieira	798492ccee	QCborValue: catch overflow in QByteArray when decoding chunked strings ... We checked against integer overflow, but not against overflowing the QByteArray size limit. That caused a std::bad_alloc to be thrown, which is bad when decoding unknown data. QCborStreamReader wasn't affected, since it doesn't merge chunks. Change-Id: I99ab0f318b1c43b89888fffd160c36f495fada87 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>	2020-05-07 07:39:26 -07:00
Thiago Macieira	783d574b93	CBOR support: prevent overflowing QByteArray's max allocation ... QByteArray doesn't like it. Apply the same protection to QString, which we know uses the same backend but uses elements twice as big. That means it can contain slightly more than half as many elements, but exact half will suffice for our needs. Change-Id: Iaa63461109844e978376fffd15f9d4c7a9137856 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>	2020-03-27 16:45:48 -03:00