This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Re: gdb 'next' problem with i386 HAL
- To: "'Jonathan Larmour'" <jlarmour at redhat dot com>
- Subject: RE: [ECOS] Re: gdb 'next' problem with i386 HAL
- From: "Stanton, Gerald" <gerald dot stanton at cacheflow dot com>
- Date: Wed, 3 Oct 2001 08:52:14 -0700
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
Hi Jonathan,
Yes, I'm using the GDB stubs from RedBoot and yes, I realized that
redboot needed to be rebuilt. However, after the cvs update yesterday,
redboot isn't building correctly. The build doesn't produce a redboot.bin
file. It only builds the include and library files. I have a tree from
last week, which successfully builds redboot.
Your response seems to imply that a fix for this problem was checked-in
at some point in time. Is this correct?
Regards,
Gerald Stanton
-----Original Message-----
From: Jonathan Larmour [mailto:jlarmour@redhat.com]
Sent: Tuesday, October 02, 2001 7:00 PM
To: Stanton, Gerald
Cc: 'ecos-discuss@sources.redhat.com'
Subject: Re: [ECOS] Re: gdb 'next' problem with i386 HAL
"Stanton, Gerald" wrote:
>
> Hi,
>
> I searched the discuss archives and found some exchanges regarding this
> problem. There didn't seem to be any resolution. I've updated via anoncvs,
> however, the problem persists. Output from GDB follows:
[snip]
Updated what from CVS? :-) If your GDB stubs are from RedBoot (the default)
you'll need to rebuild that. Or as long as you aren't using ethernet
debugging you could include stubs in your application to use the version of
stubs with the eCos sources used by your app - look in the HAL package
configuration.
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