public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: Jie Zhang <jie.zhang@analog.com>
Cc: Keith Seitz <keiths@redhat.com>, insight@sourceware.org
Subject: Re: Test insight with gdbserver
Date: Wed, 14 Jan 2009 09:52:00 -0000	[thread overview]
Message-ID: <496DB582.4060201@analog.com> (raw)
In-Reply-To: <496BFEBB.3030404@analog.com>

Jie Zhang wrote:
> Keith Seitz wrote:
>> Jie Zhang wrote:
>>> Is there a way to run gdb.gdbtk with gdbserver? It seems to me that 
>>> gdb.gdbtk cannot load program using gdbserver. Is there anything I 
>>> missed?
>>
>> If this is supported by gdb, it should work. Can you run gdb's test 
>> suite with gdbserver as the target? What does your site.exp look like?
>>
> I can run gdb's testsuite with gdbserver. But I cannot do the same for 
> insight.
> 
> It seems that insight-support.exp can only deal with four target types: 
> monitor, simulator, sid and native. Neither of them will start gdbserver 
> on target machine. It looks to me that gdb.gdbtk sets file by using 
> gdbtk_test_file and then uses the gdb commands in info(init), 
> info(target), info(load) and info(run) to start test. It does not use 
> gdb_load which is used in the other part of gdb testsuite.
> 
I now have a patch which works for me. To contribute it to Insight, is 
there any paper work about copyright I need to do? My code can be 
assigned to FSF. But the copyright line of the file I touch is 
copyrighted by Red Hat (insight-support.exp):

# GDB Testsuite Support for Insight.
#
# Copyright 2001, 2004 Red Hat, Inc.



Jie

      reply	other threads:[~2009-01-14  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 10:35 Jie Zhang
2009-01-12 16:41 ` Keith Seitz
2009-01-13  2:39   ` Jie Zhang
2009-01-14  9:52     ` Jie Zhang [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=496DB582.4060201@analog.com \
    --to=jie.zhang@analog.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).