Files
binutils-gdb/gdb/testsuite/gdb.threads/info-threads-cur-sal.exp
John Baldwin 467a34bb9e gdb tests: Allow for "LWP" or "process" in thread IDs from info threads
Several tests assume that the first word after a thread ID in 'info
threads' output is "Thread".  However, several targets use "LWP"
instead such as the FreeBSD and NetBSD native targets.  The Linux
native target also uses "LWP" if libthread_db is not being used.
Targets that do not support threads use "process" as the first word
via normal_pid_to_str.

Add a tdlabel_re global variable as a regular-expression for a thread
label in `info threads' that matches either "process", "Thread", or
"LWP".

Some other tests in the tree don't require a specific word, and
some targets may use other first words (e.g. OpenBSD uses "thread"
and Ravenscar threads use "Ravenscar Thread").
2024-03-22 17:29:47 -07:00

64 lines
2.0 KiB
Plaintext

# Copyright (C) 2013-2024 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/>.
standard_testfile info-threads-cur-sal.c info-threads-cur-sal-2.c
set executable ${testfile}
if {[gdb_compile_pthreads \
"${srcdir}/${subdir}/${srcfile} ${srcdir}/${subdir}/${srcfile2}" \
"${binfile}" executable {debug}] != "" } {
return -1
}
clean_restart ${executable}
if ![runto_main] {
return -1
}
gdb_breakpoint "start"
gdb_continue_to_breakpoint "start"
set line [gdb_get_line_number "should show this line" "${srcfile2}"]
gdb_test "list $line" \
"\"list\" should show this line.*" \
"list before info threads"
# There used to be a bug where "info threads" would set the current
# SAL to the location of the last thread displayed.
gdb_test "info threads" \
[multi_line \
"\[ \t\]*Id\[ \t\]+Target\[ \t\]+Id\[ \t\]+Frame\[ \t\]*" \
" 1 *${tdlabel_re} \[^\r\n\]* .* \[^\r\n\]*" \
"\\* 2 *${tdlabel_re} \[^\r\n\]* at \[^\r\n\]*"] \
"info threads before break"
# Check that "break" is still operating on the same file by default.
gdb_test "break $line" ".*${srcfile2}.*" "break on line"
gdb_test "info threads" \
[multi_line \
"\[ \t\]*Id\[ \t\]+Target\[ \t\]+Id\[ \t\]+Frame\[ \t\]*" \
" 1 *${tdlabel_re} \[^\r\n\]* .* \[^\r\n\]*" \
"\\* 2 *${tdlabel_re} \[^\r\n\]* at \[^\r\n\]*"] \
"info threads before list"
# And that so is "list".
gdb_test "list $line" \
"\"list\" should show this line.*" \
"list after info threads"