This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: GDB remote debug problem ??
- To: "Jonathan Larmour" <jlarmour at redhat dot com>
- Subject: Re: [ECOS] GDB remote debug problem ??
- From: "???" <jclin at itri dot org dot tw>
- Date: Wed, 4 Apr 2001 00:11:32 +0800
- Cc: <ecos-discuss at sources dot redhat dot com>
- References: <00d101c0b90c$9e560ec0$8467608c@e> <3AC4B60E.C3D97CCD@redhat.com> <001a01c0bb8c$8cfe8580$8267608c@e> <3AC8AD9C.4C320653@redhat.com>
> Ah I think I understand what you are describing - you are connecting via
> TCP to RedBoot. But then when the board hits a breakpoint, this breakpoint
> is being reported over the *serial* line, not the TCP line.
I think so. But how does it change the channel line??
> In that case, firstly make sure you are using an up-to-date anonymous CVS
> repository. Secondly, in your downloaded application's configuration, have
> you done anything like enable included GDB stubs, or claimed virtual
> vectors?
My hello application use default template, no GDB stubs included, and check
claim comms virtual vectors. I think I shouldn't include GDB stubs,but I
don't
know whether should I check the claim comms virtural vectors??
> Lastly in your port, have you done anything in the hal_diag init that
would
> cause it to claim the debug channel? Perhaps compare your diag init with
> that of another known working target, e.g. look at
> hal/arm/sa11x0/var/current/src/hal_diag.c
I copy my target from POWERPC/MBX, and I don't change any code in
hal_diag.c.
But I will check with the hal/arm/sa11x0/var/current/src/hal_diag.c
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Thanks again !!
Ken