This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
RE: insight/gdb/linux
- To: "Jonathan Larmour" <jlarmour at redhat dot co dot uk>
- Subject: RE: [ECOS] insight/gdb/linux
- From: "Alex Schuilenburg" <alexs at redhat dot com>
- Date: Tue, 20 Jun 2000 15:14:04 +0100
- Cc: <ecos-discuss at sourceware dot cygnus dot com>
- Reply-To: <alexs at redhat dot com>
> > [deleted]
> > > Is there some way to get insight to just start/continue
> > > what's already down there?
> >
> > Once you have loaded the code on the target, use the gdb console command
> > "cont". The problem w/ insight is that it uses "run" which is
> incompatible
> > with the way eCos stubs works.
>
> Why do you think this is the case? For a remote target, insight uses
> continue, as you would expect.
Not the last time I tried. Hitting the run button just issued "run", even
for remote targets. I always had to get up a console to kick start the
session. After that everything was OK.
-- Alex