diff options
| -rw-r--r-- | gdb/testsuite/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.base/expand-psymtabs.exp | 13 |
2 files changed, 16 insertions, 1 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 13b6ee2..ad481ca 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2008-01-27 Jim Blandy <jimb@codesourcery.com> + + * gdb.base/expand-psymtabs.exp: Doc fix. + 2008-01-26 Mark Kettenis <kettenis@gnu.org> * gdb.gdb/selftest.exp (do_steps_and_nexts): Add more matches. diff --git a/gdb/testsuite/gdb.base/expand-psymtabs.exp b/gdb/testsuite/gdb.base/expand-psymtabs.exp index d34a487..56742c7 100644 --- a/gdb/testsuite/gdb.base/expand-psymtabs.exp +++ b/gdb/testsuite/gdb.base/expand-psymtabs.exp @@ -20,7 +20,18 @@ if $tracelevel then { strace $tracelevel } -# Test expanding partial symtabs when needed. +# It's possible to have a program that contains two compilation units +# for the same source file name, that have code at different lines. +# For example, in this test, we compile expand-psymtabs.c twice with +# different preprocessor symbols #defined; the first .o only has +# 'main' at some earlier source lines, while the second .o only has +# 'foo' at later source lines. So when setting breakpoints by line +# number, which full symtab we need dependings on the line number in +# question. +# +# This test is meant to verify that, even with lazy partial symtab +# reading in effect, GDB can set breakpoints by line number +# successfully in either compilation unit. set testfile expand-psymtabs set srcfile ${testfile}.c |