This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: More on ethernet debugging
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: Geoff Patch <grp at cea dot com dot au>
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 06 Dec 2001 10:56:42 +0000
- Subject: Re: [ECOS] More on ethernet debugging
- References: <01C17E50.3514E5D0.grp@cea.com.au>
Geoff Patch wrote:
>
> Hi All,
>
> now that we seem to have our debugger working over the LAN more reliably, I
> have another question about its performance. On our 50MHz MPC860 targets it
> takes quite a while for each debugger command to be executed. For example,
> when singlestepping through a group of assignment statements it taked 3 - 5
> seconds for each singlestep command to execute. Stepping through more
> complicated code takes longer. In general, the interface seems to operate
> quite slowly.
>
> What I'd like to know is if this is normal and to be expected, or whether
> we may have a Bad Thing in our configuration here that is causing things to
> run suboptimally.
No, that's way too long. Does "stepi" also take the same time? A source
line singlestep may still step over many instructions (although much faster
than that, especially over the network). Try turning on remote debugging in
GDB. ( set remotedebug 1 )
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