This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: eCos Code at address 0x000? (MPC8270)
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Tim Sohacki <tsohacki at telesyn dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 18 May 2004 11:56:06 -0600
- Subject: Re: [ECOS] eCos Code at address 0x000? (MPC8270)
- Organization: MLB Associates
- References: <013b01c43cff$d7036ef0$490810ac@telesyn.corp>
On Tue, 2004-05-18 at 11:44, Tim Sohacki wrote:
> Hello,
>
> On the MPC8270, it appears that eCos has some code running at (or near)
> address 0. I suspect this is eCos specific because the first PPC
> interrupt vector stub is at 0x100.
>
> What is this code? It appears to be executed at runtime, because if it
> is trampled, the target will crash. Is it a NULL pointer write detector?
It's just a place holder - in this case, your code will just hang there
if you did a jump (or function call) to 0x0.
What do you mean "trampled" and how does the problem show up? That code
should never be executed - if it does, your program would just stop.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss