Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Nathan Sidwell <nathan@codesourcery.com>,  gdb-patches@sourceware.org
Subject: Re: add bare_board variable
Date: Wed, 19 Jul 2006 16:18:00 -0000	[thread overview]
Message-ID: <44BE5B70.4000808@codesourcery.com> (raw)
In-Reply-To: <20060719160421.GA23142@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Fri, Jun 09, 2006 at 10:09:48PM +0100, Nathan Sidwell wrote:
>> This patch adds a bare_board target_info variable to skip a couple of tests that
>> presume some kind of OS is running.
> 
> I don't really like this.  They don't presume "some OS"; the presume
> OS's with specific capabilities.
> 
> auxv.exp will only pass on Linux and solaris2; a target test would be
> OK.  Want to do that?  Just istarget; they should pass even for remote
> targets.
Ok, I'll address that

>> The start.exp test doesn't work when a gdb stub is being used.
> 
> Do you think that start should work for remote targets, and be
> equivalent to "tbreak main; continue" instead of "tbreak main; run"?
> Or maybe it should issue an error instead of trying to run?

Although 'tbreak main; continue' would be nice, it'll only work after a load, 
otherwise the state won't be right.  Or, can gdb pull the entry point address 
out of the current file and do 'tbreak main; j *<addr>' ?

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


  reply	other threads:[~2006-07-19 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 21:10 Nathan Sidwell
2006-06-16 16:36 ` Nathan Sidwell
2006-07-19 15:53 ` Nathan Sidwell
2006-07-19 16:04 ` Daniel Jacobowitz
2006-07-19 16:18   ` Nathan Sidwell [this message]
2006-07-19 16:27     ` Daniel Jacobowitz

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=44BE5B70.4000808@codesourcery.com \
    --to=nathan@codesourcery.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