From: Grant Edwards <grante@visi.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: insight@sources.redhat.com
Subject: Re: remote target => putpkt: write failed: Permission denied.
Date: Tue, 02 Oct 2001 14:13:00 -0000 [thread overview]
Message-ID: <20011115174351.A5200@visi.com> (raw)
In-Reply-To: <3BEFE4AF.42CB5E3B@cygnus.com>; from fnasser@cygnus.com on Mon, Nov 12, 2001 at 10:03:11AM -0500
On Mon, Nov 12, 2001 at 10:03:11AM -0500, Fernando Nasser wrote:
> You should not be connecting from the simulated console, specially
> in the 5.0 (old) version.
>
> Use the GUI menus to connect.
Yes, that's what I ended up doing (though I'm not keen on GUI menus, so I
generally just use "-nw" mode).
> There is a Target dialog for you to configure how and to where you want to
> connect and also menu options for connecting, disconnecting etc.
I see. The odd thing is that I've always connected via console commands when
I use the RDI target. The main advantage is you can put the target commands
in the .gdbinit file so that you don't have to do the dialog business every
time. You just type "gdb" and it connects to the target, downloads the
program, and gets everything ready to go.
> In the recent snapshots, after Keith's latest rewrites, it is
> possible that this kind of command issued from the Console Window
> properly notify the rest of the GUI (I'm not sure though), but in
> the version you are using it will just confuse it.
Yes, it certainly seems to when you use the "remote" target.
--
Grant Edwards
grante@visi.com
WARNING: multiple messages have this Message-ID
From: Grant Edwards <grante@visi.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: insight@sources.redhat.com
Subject: Re: remote target => putpkt: write failed: Permission denied.
Date: Thu, 15 Nov 2001 15:44:00 -0000 [thread overview]
Message-ID: <20011115174351.A5200@visi.com> (raw)
Message-ID: <20011115154400.qjDEjY57sW6ltrY4DSGVGqxHEYAsfmVVKQuIzV-M_Po@z> (raw)
In-Reply-To: <3BEFE4AF.42CB5E3B@cygnus.com>
On Mon, Nov 12, 2001 at 10:03:11AM -0500, Fernando Nasser wrote:
> You should not be connecting from the simulated console, specially
> in the 5.0 (old) version.
>
> Use the GUI menus to connect.
Yes, that's what I ended up doing (though I'm not keen on GUI menus, so I
generally just use "-nw" mode).
> There is a Target dialog for you to configure how and to where you want to
> connect and also menu options for connecting, disconnecting etc.
I see. The odd thing is that I've always connected via console commands when
I use the RDI target. The main advantage is you can put the target commands
in the .gdbinit file so that you don't have to do the dialog business every
time. You just type "gdb" and it connects to the target, downloads the
program, and gets everything ready to go.
> In the recent snapshots, after Keith's latest rewrites, it is
> possible that this kind of command issued from the Console Window
> properly notify the rest of the GUI (I'm not sure though), but in
> the version you are using it will just confuse it.
Yes, it certainly seems to when you use the "remote" target.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-11-15 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 12:30 Grant Edwards
2001-10-01 6:51 ` Fernando Nasser
2001-10-02 14:13 ` Grant Edwards [this message]
2001-10-02 14:24 ` Tom Tromey
2001-11-15 16:14 ` Tom Tromey
2001-11-15 15:44 ` Grant Edwards
2001-11-12 7:04 ` Fernando Nasser
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=20011115174351.A5200@visi.com \
--to=grante@visi.com \
--cc=fnasser@cygnus.com \
--cc=insight@sources.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).