Bug 255494 - illegal opcode memcpy in /lib/ld-2.8.so
Summary: illegal opcode memcpy in /lib/ld-2.8.so
Status: RESOLVED UNMAINTAINED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.6.0
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-28 13:54 UTC by linuxpenseur
Modified: 2024-11-10 20:17 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The error log file obtained when Valgrind-3.6.0 was run on sample executable file (2.75 KB, text/plain)
2010-10-28 13:54 UTC, linuxpenseur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description linuxpenseur 2010-10-28 13:54:48 UTC
Created attachment 52939 [details]
The error log file obtained when Valgrind-3.6.0 was run on sample executable file

I am running Valgrind-3.6.0 on PowerPC machine.

The details of the PowerPC processor is given below :

*********************************************

processor       : 0
cpu             : e500v2
clock           : 799.999992MHz
revision        : 5.0 (pvr 8021 1050)
bogomips        : 99.84

total bogomips  : 99.84
timebase        : 50000000
platform        : P2020 DS
model           : fsl,P2020

*********************************************

I get the correct version of Valgrind when i run the command "valgrind --version"

But when i use valgrind on a sample executable file "temp", i get the following error message.

*******************************************

==19630==  Illegal opcode at address 0x4019510
==19630==    at 0x4019510: memcpy (in /lib/ld-2.8.so)
==19630==    by 0x40021BF: _dl_start_final (in /lib/ld-2.8.so)
==19630==    by 0x40162C7: _start (in /lib/ld-2.8.so)

********************************************

The detailed error log is attached with this bug report.
Comment 1 Julian Seward 2011-01-10 21:04:54 UTC
We don't support e500 currently, sorry.
Comment 2 rio 2013-04-02 09:55:22 UTC
Would there be any schedule to add PPC e500v2 support?
Comment 3 Carl Love 2024-06-24 15:43:03 UTC
There is no schedule to add PPC e500v2 support.
Comment 4 Paul Floyd 2024-11-10 20:17:28 UTC
I think that we can close this one.