summaryrefslogtreecommitdiffstats
path: root/mkspecs/features/qt_common.prf
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@intel.com>2018-12-11 12:48:12 -0800
committerThiago Macieira <thiago.macieira@intel.com>2018-12-14 18:25:28 +0000
commit3e4f8aa8f434d791b3dfe9450bad85b82406d4b3 (patch)
tree79c2abb8f55cc8ce28583288cab0b441e5dbd397 /mkspecs/features/qt_common.prf
parent3c3a2eb3cea0bbb0b45e43278421e051c253e434 (diff)
Doc: fix null pointer passing to fprintf
When these docs were written, the context.file and context.function pointers were never null. But in commit d78fb442d750b33afe2e41f31588ec94 (Qt 5.4), we made the logging pass null pointers in release builds. The C standard does not say that passing null pointers is permitted. In fact, it says "If no l length modifier is present, the argument shall be a pointer to the initial element of an array of character type." and that's pretty explicit that it needs to point to the initial element of a string. Fixes: QTBUG-72478 Change-Id: I4ac1156702324f0fb814fffd156f624ffefa1445 Reviewed-by: Topi Reiniƶ <topi.reinio@qt.io>
Diffstat (limited to 'mkspecs/features/qt_common.prf')
0 files changed, 0 insertions, 0 deletions