public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <kseitz@firetalk.com>
To: Paul Breed <paul@Netburner.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: .gdbinit initialization and GUI...
Date: Mon, 10 Jul 2000 06:34:00 -0000	[thread overview]
Message-ID: <3969D0F4.8B7A42F4@firetalk.com> (raw)
In-Reply-To: <4.2.0.58.20000710092726.0214de50@pop.netburner.com>

Paul Breed wrote:
> 
> >
> >Simple. Using the target dialog, click the "more options" button to
> >reveal the hidden pane. The options here are the default actions taken
> >when the user presses the Run button. Simply turn off "Download" and
> >"Attach" and keep "Continue".
> This did not work.
> IT still brings up the target dialog when I hit run.
> Even though I've already connected to the target with the  script.

Doh! Yes, it will do that. This is another one of those GUI-command line
disconnect issues. We never did fix that properly...

On the other hand, now that I think about it, you don't really need to
put this sort of thing into a startup script -- the Insight GUI will
automatically attach, download, and start the program for you when you
press the Run button (depending on the settings in the Target Selection
Dialog). It will also remember these settings, so that the next time you
run the debugger, it will "do the right thing". Of course, when you
first the debugger, it will ALWAYS bring up the Target Dialog and ask
for your target, in case you intend to connect to a different target.
Are you trying to just bypass the dialog so that you never see it?

Keith

  parent reply	other threads:[~2000-07-10  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-09 13:48 Paul Breed
2000-07-10  5:32 ` Keith Seitz
     [not found] ` <4.2.0.58.20000710092726.0214de50@pop.netburner.com>
2000-07-10  6:34   ` Keith Seitz [this message]
2000-07-10 10:46 ` Jim Ingham

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=3969D0F4.8B7A42F4@firetalk.com \
    --to=kseitz@firetalk.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=paul@Netburner.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).