Ryan Mansfield(deleted)
|
Re: memcpy and memset crashes with SIGSEGV
|
Ryan Mansfield(deleted)
10/06/2010 9:21 AM
post69730
|
Re: memcpy and memset crashes with SIGSEGV
On 10-10-06 08:19 AM, Girisha SG wrote:
> 1. I could not find the way by which I can change the build variant in
> the BSP release.
In the build file modify it to [virtual=armle-v7] then under the
components add the corresponding v7 build variants directories. e.g.
o.le.v7 or a.le.v7 or so.le.v7
> 2. I have replaced the contents of armle folder with armlev7 binaries
> but it complains about mismatch of EABI(It says some thing like source
> is EABI 0 but xyz is EABI 5).
No, don't do this. But this means you're still building the part of the
image with armle..
> 3. I have asked BSP forum for 6.5.0 BSP for armle-v7 release. But there
> is no concluding remarks.
Which BSP is this for? Either you have to switch the BSP to armle
yourself, or get a working BSP. Ask again in the forums. Do not proceed
until you have a working armle-v7 BSP running on the target. If your
target is a mismatched with ABI variants, you're going to have endless
headaches. If you can't get a working BSP going, then have to stick with
an armle variant, which means you will have to use gcc instead of RVDS.
BTW, what is your motivation behind using RVDS? Your reasons must pretty
motivating considering this is an unsupported configuration.
> 4. [RM]:It sounds like you may have an armle libc running on your target
> which will cause more issues for you.
> [GG]:Yes it was the case
It's still an issue. If you haven't changed the build file, then it
means the libc in your image is armle.
> 5. The sources are modified a bit to have our own memcpy, memset,
> __aeabi_memcpy, __aeabi_memcpy4, __aeabi_memclr etc and hence the line
> numbers are not exactly aligned between the two cases(ofcourse this was
> without using -Ono_memcpy option :)).
Whether you provide your own implementations of functions shouldn't
really matter. If anything you should be able to debug these as you have
the source to these functions.
Regards,
Ryan Mansfield
|
|
|