f6512a69cd
I couldn't find a test that verified the thread name functionality, so I created a new one. A target board can define gdb,no_thread_names if it doesn't support thread names and wants to skip the tests that uses them. This test has been made with Linux in mind. Not all platforms use pthread_setname_np to set the thread name, but some #ifdefs can be added later in order to support other platforms. Tested on x86-64 Ubuntu 14.04, native and remote. gdb/testsuite/ChangeLog: * gdb.threads/names.exp: New file. * gdb.threads/names.c: New file. * README: Mention gdb,no_thread_names.
38 lines
1.2 KiB
Text
38 lines
1.2 KiB
Text
# Copyright (C) 2015 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
# Verify that thread name features work properly (e.g. they show up in info
|
|
# threads).
|
|
|
|
if [target_info exists gdb,no_thread_names] {
|
|
continue
|
|
}
|
|
|
|
standard_testfile
|
|
|
|
if [prepare_for_testing "failed to prepare" $testfile $srcfile {debug pthreads}] {
|
|
return -1
|
|
}
|
|
|
|
if ![runto "all_threads_ready"] {
|
|
continue
|
|
}
|
|
|
|
gdb_test "info threads" \
|
|
[multi_line "\\* 1 .*\"main\" all_threads_ready.*" \
|
|
" 2 .*\"carrot\".*" \
|
|
" 3 .*\"potato\".*" \
|
|
" 4 .*\"celery\".*" ] \
|
|
"list threads"
|