mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-03-13 13:49:00 +08:00
explicitly test for stderr in gdb.base/dprintf.exp
Not all compilers add stderr debug information when compiling a program. Clang, for instance, prefers to add nothing from standard libraries and let an external debug package have this information. Because of this, gdb.base/dprintf.exp was failing when GDB attempted to use dprintf as a call to fprintf(stderrr, ...), like this: (gdb) PASS: gdb.base/dprintf.exp: call: fprintf: set dprintf style to call continue Continuing. kickoff 1234 also to stderr 1234 'stderr' has unknown type; cast it to its declared type (gdb) FAIL: gdb.base/dprintf.exp: call: fprintf: 1st dprintf (timeout) To avoid this false positive, we explicitly test to see if the compiler has added information about stderr at all, and abort testing dprintf as an fprintf call if it is unavailable.
This commit is contained in:
parent
6a69b0a180
commit
3f5bbc3e20
@ -111,6 +111,16 @@ proc test_call {} {
|
||||
test_dprintf "At foo entry.*arg=1235, g=2222\r\n" "2nd dprintf"
|
||||
}
|
||||
|
||||
gdb_test_multiple "print stderr" "stderr symbol check" {
|
||||
-re "\\'stderr\\' has unknown type.*" {
|
||||
untested "No information available for stderr, exiting early"
|
||||
return
|
||||
}
|
||||
-re "\\\$1.*" {
|
||||
pass $gdb_test_name
|
||||
}
|
||||
}
|
||||
|
||||
with_test_prefix "fprintf" {
|
||||
restart
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user