This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: ARM Simulator Bug?
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: mckennad at esatclear dot ie
- Cc: Richard Earnshaw <rearnsha at arm dot com>, gdb at sources dot redhat dot com, insight at sources dot redhat dot com, Richard dot Earnshaw at arm dot com
- Date: Wed, 03 Sep 2003 14:53:21 +0100
- Subject: Re: ARM Simulator Bug?
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Hi Richard,
>
> I think I have gotten closer to solving my problem. It relates to the linker
> script I use with compilation of gcc.
>
> If I take the standard armelf.x from the ldscripts directory and link against
> it my problem disappears. My problem is that I wish to place my reset vectors
> at 0x00 not the standard 0x8000. So I change the line:
>
> /* Read-only sections, merged into text segment: */
> . = 0x8000;
>
> to
>
> /* Read-only sections, merged into text segment: */
> . = 0x00;
>
> and my problem resurfaces. At a quick check of my memory contents from gdb at
> 0x00 I get 0x01 as opposed to what I get when I "download" the program using
> Run->Download of 0xEA000015.
>
> Any ideas?
Not really. Does "arm-elf-objdump -xd exe-file" display something
sensible?
R.