Re: remote target => putpkt: write failed: Permission denied.

[Tom Tromey <tromey@redhat.com>]

>>>>> "Grant" == Grant Edwards <grante@visi.com> writes:

Grant> I see. The odd thing is that I've always connected via console
Grant> commands when I use the RDI target.

I think it is important that Insight continue to support the habits of
those switching from the command-line gdb.  However, Insight hacking
time has historically been limited, so this doesn't always happen --
perfectly understandable imo.

Feel like doing some Insight hacking? :-)
Failing that maybe a PR is the best bet.

Grant> The main advantage is you can put the target commands in the
Grant> .gdbinit file so that you don't have to do the dialog business
Grant> every time.  You just type "gdb" and it connects to the target,
Grant> downloads the program, and gets everything ready to go.

Ideally we could extend sessions to capture this information.  I
rarely do any non-native debugging, so when I wrote the session code I
didn't add this feature.  There is some minimal support for it;
expanding it would make a lot of sense.  I think it would be best if
this work (or at least a specification for it) were done by someone
who is really familiar with non-native debugging.

Tom