gcore-thread.exp

来自「模拟嵌入式硬件平台的软件源代码」· EXP 代码 · 共 187 行

EXP
187
字号
# Copyright 2002 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 2 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, write to the Free Software# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  # Please email any bugs, comments, and/or additions to this file to:# bug-gdb@prep.ai.mit.edu# This file was written by Michael Snyder (msnyder@redhat.com)# This is a test for the gdb command "generate-core-file".if $tracelevel then {	strace $tracelevel}set prms_id 0set bug_id 0# Single-threaded test caseset testfile "pthreads"set srcfile  ${testfile}.cset binfile  ${objdir}/${subdir}/${testfile}set built_binfile 0if [istarget "*-*-linux"] then {    set target_cflags "-D_MIT_POSIX_THREADS"} else {    set target_cflags ""}set why_msg "unrecognized error"foreach lib {-lpthreads -lpthread -lthread} {    set options "debug"    lappend options "incdir=${objdir}/${subdir}"    lappend options "libs=$lib"    set ccout [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable $options]    switch -regexp -- $ccout {	".*no posix threads support.*" {	    set why_msg "missing threads include file"	    break	}	".*cannot open -lpthread.*" {	    set why_msg "missing runtime threads library"	}	".*Can't find library for -lpthread.*" {	    set why_msg "missing runtime threads library"	}	{^$} {	    pass "successfully compiled posix threads test case"	    set built_binfile 1	    break	}    }}if {$built_binfile == "0"} {    unsupported "Couldn't compile ${srcfile}, ${why_msg}"    return -1}# Now we can proceed with the real testing.# Start with a fresh gdb.gdb_exitgdb_startgdb_reinitialize_dir $srcdir/$subdirgdb_load ${binfile}# regexp for "horizontal" text (i.e. doesn't include newline or# carriage return)set horiz "\[^\n\r\]*"# regexp for newlineset nl "\[\r\n\]+"set timeout 30send_gdb "help gcore\n"gdb_expect {    -re "Undefined command: .gcore.*$gdb_prompt $" {	# gcore command not supported -- nothing to test here.	unsupported "gdb does not support gcore on this target"	return -1;    }    -re "Save a core file .*$gdb_prompt $" {	pass "help gcore"    }    -re ".*$gdb_prompt $" {	fail "help gcore"    }    timeout {	fail "help gcore (timeout)"    }}if { ! [ runto main ] } then {    gdb_suppress_entire_file "Run to main failed, so all tests in this file will automatically fail."}send_gdb "info threads\n"gdb_expect {    -re ".* main .*$gdb_prompt $" {	# OK, threads are supported.    }    -re "${nl}$gdb_prompt $" {	unsupported "gdb does not support threads on this target"	return -1;    }}# Make sure thread 1 is runningdelete_breakpointsgdb_breakpoint "thread1"gdb_test "continue" "Continuing.*Breakpoint.* thread1 .*" "thread 1 is running"# Make sure thread 2 is runningdelete_breakpointsgdb_breakpoint "thread2"gdb_test "continue" "Continuing.*Breakpoint.* thread2 .*" "thread 2 is running"# Drop corefilegdb_test "gcore ${objdir}/${subdir}/gcore.test" \	"Saved corefile ${objdir}/${subdir}/gcore.test" \	"save a corefile"# Now restart gdb and load the corefile.gdb_exitgdb_startgdb_reinitialize_dir $srcdir/$subdirgdb_load ${binfile}send_gdb "core ${objdir}/${subdir}/gcore.test\n"gdb_expect {    -re ".* is not a core dump:.*$gdb_prompt $" {	fail "re-load generated corefile (bad file format)"	# No use proceeding from here.	return;	    }    -re ".*: No such file or directory.*$gdb_prompt $" {	fail "re-load generated corefile (file not found)"	# No use proceeding from here.	return;	    }    -re ".*Couldn't find .* registers in core file.*$gdb_prompt $" {	fail "re-load generated corefile (incomplete note section)"    }    -re "Core was generated by .*$gdb_prompt $" {	pass "re-load generated corefile"    }    -re ".*$gdb_prompt $" {	fail "re-load generated corefile"    }    timeout {	fail "re-load generated corefile (timeout)"    }}# FIXME: now what can we test about the thread state?# We do not know for certain that there should be at least # three threads, because who knows what kind of many-to-one# mapping various OS's may do?  Let's assume that there must# be at least two threads:gdb_test "info threads" ".*${nl}  2 ${horiz}${nl}\\* 1 .*" \	"corefile contains at least two threads"# One thread in the corefile should be in the "thread2" function.gdb_test "info threads" ".* thread2 .*" \	"a corefile thread is executing thread2"# The thread2 thread should be marked as the current thread.gdb_test "info threads" ".*${nl}\\* ${horiz} thread2 .*" \	"thread2 is current thread in corefile"

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?