diff options
| author | Juro Bystricky <juro.bystricky@intel.com> | 2017-08-04 15:40:54 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-08-13 09:27:38 +0100 |
| commit | b9b6ede7f8a191b82e8c8c711ad7425fa774c876 (patch) | |
| tree | ed6c8118d07e493a18ce24aca76c249f69ea2f0c /meta/lib/oeqa/selftest/cases/buildoptions.py | |
| parent | 9952b38de4002da66da677380ac86283f852ad22 (diff) | |
| download | poky-b9b6ede7f8a191b82e8c8c711ad7425fa774c876.tar.gz | |
gcc7: fix potential segmentation fault
Under some rare circumstances we may end up with GCC segmentation fault.
This was observed with versions of sysmacros.h, which contain macros
with embedded warning messages :
When trying to actually display the warning, we may end up with a segmentation
fault instead. The reason is the actual warning message gets parsed (the text is
unquoted) and words in the message such as "not", "and" etc. are interpreted as
operators CPP_NOT, CPP_AND. When the time comes to display the warning, the code
uses wrong structure to access the "name" corresponding to the operators.
[YOCTO #11738]
(From OE-Core rev: 6f81fe4f3a1177c0049b26a070e43546bc6fe974)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oeqa/selftest/cases/buildoptions.py')
0 files changed, 0 insertions, 0 deletions