From: Pedro Alves <pedro@codesourcery.com>
To: "Wei-cheng Wang" <cole945@gmail.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [testsuite] setting sysroot for target-board
Date: Mon, 09 May 2011 11:39:00 -0000 [thread overview]
Message-ID: <201105091239.47267.pedro@codesourcery.com> (raw)
In-Reply-To: <BANLkTimm53SZvTrAn6SHzSE9B=fw-YKqkw@mail.gmail.com>
On Sunday 08 May 2011 18:01:16, Wei-cheng Wang wrote:
> On Fri, May 6, 2011 at 5:47 PM, Pedro Alves <pedro@codesourcery.com> wrote:
> > On Friday 06 May 2011 03:24:08, Wei-cheng Wang wrote:
> > Doing this here assumes you'll only need the sysroot after connecting.
> > How have you tested this? It seems you forgot the MI equivalent.
> Yes, I did test it.
> I found this issue when I tested gdb/gdbserver with a remote
> cross-target. Some thread- and shared library-related test cases
> failed due to using the wrong shared libraries for the host, so I
> tried to add sysroot support and I’ve tested it again to make sure gdb
> will use the right shared libraries for the target.
> > I think a better place would be right after spawning
> > gdb (default_gdb_start/default_mi_gdb_start). If since you
> > already have a board file anyway, you could also override *gdb_start
> > and do it there instead of adding a new flag.
> I agree. It’s better to put this in default_gdb_start/default_mi_gdb_start.
> Since these two functions are not just a few of lines,
You'd override "gdb_start", which is already a hook, not default_gdb_start
itself:
proc gdb_start { } {
default_gdb_start
}
You can also override big functions in tcl and rename/call
the overridden version, so that the fact that the functions
are big is not a problem, though that's a bit hackish.
> I will suggest adding this support, so it much easier to set sysroot as needed.
Agreed.
> And here is the update according to your suggestion. Thanks.
Thanks. The tab/space/indenting looked a bit off, not sure
that's just patch/email tricking me, but otherwise looks
good to me.
> - - - -
> 2011-05-06 Wei-cheng Wang <cole945@gmail.com>
>
> * lib/gdb.exp (default_gdb_start): Add support for setting sysroot for
> target system.
> * lib/mi-support.exp (default_mi_gdb_start): Likewise.
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 20e2fb7..c6fa62d 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -1349,6 +1349,18 @@ proc default_gdb_start { } {
> warning "Couldn't set the width to 0."
> }
> }
> +
> + if [target_info exists gdb,sysroot] {
> + send_gdb "set sysroot [target_info gdb,sysroot]\n"
> + gdb_expect 10 {
> + -re "$gdb_prompt $" {
> + verbose "Setting sysroot to [target_info gdb,sysroot]" 2
> + }
> + timeout {
> + warning "Couldn't set the sysroot to [target_info gdb,sysroot]"
> + }
> + }
> + }
> return 0;
> }
>
> diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
> index e1dbd19..15565bc 100644
> --- a/gdb/testsuite/lib/mi-support.exp
> +++ b/gdb/testsuite/lib/mi-support.exp
> @@ -221,6 +221,17 @@ proc default_mi_gdb_start { args } {
> }
> }
> }
> + if [target_info exists gdb,sysroot] {
> + send_gdb "103-gdb-set sysroot [target_info gdb,sysroot]\n"
> + gdb_expect 10 {
> + -re ".*103-gdb-set sysroot [target_info
> gdb,sysroot]\r\n103\\\^done\r\n$mi_gdb_prompt$" {
> + verbose "Setting sysroot to [target_info gdb,sysroot]" 2
> + }
> + timeout {
> + warning "Couldn't set the sysroot to [target_info gdb,sysroot]."
> + }
> + }
> + }
>
> detect_async
>
--
Pedro Alves
prev parent reply other threads:[~2011-05-09 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 8:09 Wei-cheng Wang
2011-05-05 17:37 ` Tom Tromey
2011-05-06 2:24 ` Wei-cheng Wang
2011-05-06 9:47 ` Pedro Alves
2011-05-08 17:01 ` Wei-cheng Wang
2011-05-09 11:39 ` Pedro Alves [this message]
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=201105091239.47267.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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