From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3020 invoked by alias); 16 Nov 2001 00:14:45 -0000 Mailing-List: contact insight-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 2984 invoked from network); 16 Nov 2001 00:14:39 -0000 To: Grant Edwards Cc: Fernando Nasser , insight@sources.redhat.com Subject: Re: remote target => putpkt: write failed: Permission denied. References: <20011107143449.A24299@visi.com> <3BEFE4AF.42CB5E3B@cygnus.com> <20011115174351.A5200@visi.com> X-Zippy: Look!! Karl Malden! X-Attribution: Tom Reply-To: tromey@redhat.com From: Tom Tromey Date: Tue, 02 Oct 2001 14:24:00 -0000 In-Reply-To: Grant Edwards's message of "Thu, 15 Nov 2001 17:43:56 -0600" Message-ID: <874rnvtur7.fsf@creche.redhat.com> X-Mailer: Gnus v5.7/Emacs 20.5 X-SW-Source: 2001-q4/txt/msg00014.txt.bz2 >>>>> "Grant" == Grant Edwards 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey To: Grant Edwards Cc: Fernando Nasser , insight@sources.redhat.com Subject: Re: remote target => putpkt: write failed: Permission denied. Date: Thu, 15 Nov 2001 16:14:00 -0000 Message-ID: <874rnvtur7.fsf@creche.redhat.com> References: <20011107143449.A24299@visi.com> <3BEFE4AF.42CB5E3B@cygnus.com> <20011115174351.A5200@visi.com> X-SW-Source: 2001-q4/msg00315.html Message-ID: <20011115161400.-jssnth0ARw-3WuDIEAv4_A3KN1d7-T06FUV8cFnc4g@z> >>>>> "Grant" == Grant Edwards 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