[Fwd: RE: question about run download sequence]

[Keith Seitz <keiths at redhat dot com>]

For archival.

-----Forwarded Message-----

> From: Aaron Case <aaron.case@dynazign.com>
> To: Keith Seitz <keiths@redhat.com>
> Subject: RE: question about run download sequence
> Date: 20 Jun 2003 15:22:05 -0400
> 
> Keith,
> 
> Typing continue in the command window fixed the issue.
> 
> Thanks for your help.
> 
> Aaron Case
> 
> Dynazign, Inc
> Charlotte, NC
> 
> -----Original Message-----
> From: Keith Seitz [mailto:keiths@redhat.com]
> Sent: Friday, June 20, 2003 11:12 AM
> To: Aaron Case
> Cc: insight@sources.redhat.com
> Subject: RE: question about run download sequence
> 
> 
> On Fri, 2003-06-20 at 08:40, Aaron Case wrote:
> 
> > 5)Next I try to download Connect->Download the code to the target. This
> > appears to work and gives a message indicating that the file was
> downloaded.
> >
> > 6)Then I click Connect->Run.  This is where the problems begin. Insight
> then
> > gets stuck in an infinite loop of downloading and popping up the target
> > settings box with no way to exit.
> 
> Ok, that's the problem. One does not use "run" on remote targets. This
> is a gdb policy. It has to do with gdb's staunch assertion that run
> actually creates an inferior PROCESS. Remote boards don't have processes
> (at least in gdb's view of the board). Use "continue" instead. The
> download will have set the PC to the entry address in the file. This is
> essentially the same as "running" it. It's a little technical, but,
> well, that's the way gdb works.
> 
> I recommend NOT doing steps 5 & 6. Instead, just click the run button.
> It will do the download and automatically continue the target. (These
> settings can be modified in the Target Settings dialog. Click "More
> options".)
> 
> Let me know how that goes.
> 
> Keith
> 
> 
>