From: Daniel Jacobowitz <drow@false.org>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Cc: GDB Patches Mailing List <gdb-patches@sourceware.org>
Subject: Re: [patch] Expand psymtabs when needed - testcase
Date: Sun, 16 Dec 2007 21:58:00 -0000 [thread overview]
Message-ID: <20071216215352.GG2618@caradoc.them.org> (raw)
In-Reply-To: <4755C969.6040001@linux.vnet.ibm.com>
On Tue, Dec 04, 2007 at 07:40:57PM -0200, Carlos Eduardo Seo wrote:
> Is this OK?
Almost, thanks.
> 2007-12-04 Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
> Jim Blandy <jimb@codesourcery.com>
>
> * testsuite/gdb.base/expand-psymtabs.c: New testcase
> source file.
> * testsuite/gdb.base/expand-psymtabs.exp: New testcase
> expect file.
Since this goes in testsuite/ChangeLog, don't use the "testsuite/"
prefix in the entry.
> Index: src/gdb/testsuite/gdb.base/expand-psymtabs.c
> ===================================================================
> --- /dev/null
> +++ src/gdb/testsuite/gdb.base/expand-psymtabs.c
> @@ -0,0 +1,22 @@
> +#include <stdio.h>
Every new file should have a copyright notice, even in the testsuite.
Also, please avoid using I/O if you don't need it; that limits which
targets can run the test.
> +if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile_1}" object {debug nowarnings additional_flags=-DFIRST} ] != "" } {
Why nowarnings?
> +# use this to debug:
> +log_user 1
Delete this.
> +gdb_exit
> +gdb_start
> +gdb_reinitialize_dir $srcdir/$subdir
> +gdb_load ${binfile}
> +
> +gdb_test "break 20" "Breakpoint.*" "Expand psymtabs"
Don't use hardcoded line numbers. Look for an example using
gdb_get_line_number instead to find the right line, unless there's
some reason that won't work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-16 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 21:41 Carlos Eduardo Seo
2007-12-16 21:58 ` Daniel Jacobowitz [this message]
2007-12-17 0:56 ` Carlos Eduardo Seo
2007-12-17 1:49 ` Daniel Jacobowitz
2007-12-17 3:45 ` Thiago Jung Bauermann
2007-12-17 16:46 ` Carlos Eduardo Seo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071216215352.GG2618@caradoc.them.org \
--to=drow@false.org \
--cc=cseo@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox