public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Grant Edwards <grante@visi.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Can't get "run" button to work
Date: Tue, 03 Oct 2000 14:13:00 -0000	[thread overview]
Message-ID: <39DA4BEC.C382E1A2@cygnus.com> (raw)
In-Reply-To: <20000828183709.B6810@visi.com>

Grant Edwards wrote:
> 
> The one thing I've left to try is to re-write the "after
> attach" command so that that it initializes the hardware, then
> downloads/runs the memconfig program without using symbols.
> I'd have to hard-wire a break point, but that program never
> changes, so it might work...
> 
Humm... would a "before attach" help?  Just thinking aloud...


-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  parent reply	other threads:[~2000-10-03 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-28 15:53 Grant Edwards
     [not found] ` <20000828181002.A6810@visi.com>
     [not found]   ` <20000828183709.B6810@visi.com>
2000-10-03 14:13     ` Fernando Nasser [this message]
2000-10-03 14:21       ` Grant Edwards

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=39DA4BEC.C382E1A2@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=grante@visi.com \
    --cc=insight@sourceware.cygnus.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).