aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/gdbint.texinfo
diff options
context:
space:
mode:
authorJan Kratochvil <jan.kratochvil@redhat.com>2011-12-19 13:37:34 +0000
committerJan Kratochvil <jan.kratochvil@redhat.com>2011-12-19 13:37:34 +0000
commit13ac8d2c29bd346711448e3d6630d231e46fb70d (patch)
treee3406b81c583ed43e1393b4ae1b6b9a78406434f /gdb/doc/gdbint.texinfo
parenta53e62cf5654e07a8d78ce5c8f7d386565c2c17d (diff)
downloadgdb-13ac8d2c29bd346711448e3d6630d231e46fb70d.zip
gdb-13ac8d2c29bd346711448e3d6630d231e46fb70d.tar.gz
gdb-13ac8d2c29bd346711448e3d6630d231e46fb70d.tar.bz2
gdb/doc/
* gdbint.texinfo (Testsuite): Describe KFAIL and XFAIL in Writing tests. gdb/testsuite/ * gdb.cp/ptype-cv-cp.exp (ptype v_volatile_const_my_int): Replace KFAIL by XFAIL. * gdb.cp/static-method.exp (info addr A::func()) (list static-method.cc:xxx::(anonymous namespace)::A::func) (list 'static-method.cc:xxx::(anonymous namespace)::A::func') (list 'static-method.cc':'xxx::(anonymous namespace)::A::func') (list static-method.cc:'xxx::(anonymous namespace)::A::func'): Likewise. * gdb.cp/temargs.exp (test value of F in k2_m, test type of F in k3_m) (test value of F in k3_m): Likewise. * gdb.python/py-type.exp (python print ttype.template_argument(2)): Likewise.
Diffstat (limited to 'gdb/doc/gdbint.texinfo')
-rw-r--r--gdb/doc/gdbint.texinfo39
1 files changed, 39 insertions, 0 deletions
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 20791b4..cd4d492 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -7846,6 +7846,45 @@ instance, some @value{GDBN} bugs involving the display of source lines would
never manifest themselves if the programs used GNU coding style
uniformly.
+Some testcase results need more detailed explanation:
+
+@table @code
+@item KFAIL
+Known problem of @value{GDBN} itself. You must specify the @value{GDBN} bug
+report number like in these sample tests:
+@smallexample
+kfail "gdb/13392" "continue to marker 2"
+@end smallexample
+or
+@smallexample
+setup_kfail gdb/13392 "*-*-*"
+kfail "continue to marker 2"
+@end smallexample
+
+@item XFAIL
+Known problem of environment. This typically includes @value{NGCC} but it
+includes also many other system components which cannot be fixed in the
+@value{GDBN} project. Sample test with sanity check not knowing the specific
+cause of the problem:
+@smallexample
+# On x86_64 it is commonly about 4MB.
+if @{$stub_size > 25000000@} @{
+ xfail "stub size $stub_size is too large"
+ return
+@}
+@end smallexample
+
+You should provide bug report number for the failing component of the
+environment, if such bug report is available:
+@smallexample
+if @{[test_compiler_info @{gcc-[0-3]-*@}]
+ || [test_compiler_info @{gcc-4-[0-5]-*@}]@} @{
+ setup_xfail "gcc/46955" *-*-*
+@}
+gdb_test "python print ttype.template_argument(2)" "&C::c"
+@end smallexample
+@end table
+
@node Hints
@chapter Hints