diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2015-07-27 15:49:24 -0400 |
---|---|---|
committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-07-27 15:49:24 -0400 |
commit | 13e1dec8960122ec0329f74e5915503e14db5ea2 (patch) | |
tree | c32be51b725795b0fc6cbc188ab32072e3abee23 /gdb/testsuite/gdb.mi/basics.c | |
parent | da33c9a7bff093e772a381bf9ab42d876089cdcf (diff) | |
download | gdb-13e1dec8960122ec0329f74e5915503e14db5ea2.zip gdb-13e1dec8960122ec0329f74e5915503e14db5ea2.tar.gz gdb-13e1dec8960122ec0329f74e5915503e14db5ea2.tar.bz2 |
gdb.mi/mi-pending.c: Return NULL instead of nothing in thread function
Using gcc 5.2 (maybe other versions as well), building mi-pending.c gives
these warnings:
./gdb.mi/mi-pending.c: In function ‘thread_func’:
./gdb.mi/mi-pending.c:34:5: warning: ‘return’ with no value, in function returning non-void
return;
^
./gdb.mi/mi-pending.c:38:5: warning: ‘return’ with no value, in function returning non-void
return;
^
gdb_compile_pthreads assumes that the build was successful only if there
is no output. These warnings therefore make gdb_compile_pthreads think
that the build failed, and the test doesn't run.
The easy fix is to replace the "return" with "return NULL". I am
pushing this as obvious.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-pending.c (thread_func): Replace return with return
NULL.
Diffstat (limited to 'gdb/testsuite/gdb.mi/basics.c')
0 files changed, 0 insertions, 0 deletions