darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2025-02-15 23:18:03 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdb.base/corefile.exp: When generating a core, discard any

Browse Source 
error messages about ulimit not found and the "core dumped"
	message from the shell that runs the coredumper.
This commit is contained in:
Fred Fish 1996-01-04 21:12:12 +00:00
parent 7531f36e8e
commit 4b2dd77883
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
Thu Jan 4 08:17:22 1996 Fred Fish <fnf@cygnus.com>
* gdb.base/corefile.exp: When generating a core, discard any
error messages about ulimit not found and the "core dumped"
message from the shell that runs the coredumper.
Wed Jan 3 01:30:41 1996 Jeffrey A Law (law@cygnus.com)
* lib/gdb.exp (skip_chill_tests): Skip them on the PA too.

8
gdb/testsuite/gdb.base/corefile.exp
View File

@ -57,7 +57,7 @@ if ![file exists ${objdir}/${subdir}/corefile] then {
# Some systems append "core" to the name of the program; others append
# the name of the program to "core".
set found 0
catch "system \"cd ${objdir}/${subdir}; ulimit -c unlimited; ${binfile}\""
catch "system \"(cd ${objdir}/${subdir}; ulimit -c unlimited; ${binfile}; true) >/dev/null 2>&1\""
# execute_anywhere "${binfile}"
foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
set exec_output [execute_anywhere "ls $i"]
@ -164,16 +164,14 @@ gdb_test "print coremaker_data" "\\\$$decimal = 202"
gdb_test "print coremaker_bss" "\\\$$decimal = 10"
gdb_test "print coremaker_ro" "\\\$$decimal = 201"
# Linux GDB is unable to backtrace properly from an abort system call,
# so trying to access a local variable in the stack fails too.
setup_xfail "i*86-*-linux*" "i*86-*-sysv4*"
setup_xfail "i*86-*-sysv4*"
gdb_test "print func2::coremaker_local" "\\\$$decimal = {0, 1, 2, 3, 4}"
# Somehow we better test the ability to read the registers out of the core
# file correctly. I don't think the other tests do this.
# Haven't investigated this xfail
setup_xfail "m68k-*-hpux*" "i*86-*-linux*" "i*86-*-sysv4*"
setup_xfail "m68k-*-hpux*" "i*86-*-sysv4*"
# Strange that this one depends upon being native compiled.
gdb_test "bt" "abort.*func2.*func1.*main.*" "backtrace in corefile.exp"