| Summary: | Valgrind is missing an armv7 instruction | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Alberto Ruiz <aruiz> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | peter.maydell |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Looks like the same as bug 344082 to me (insn is reading CNTVCT). Doh, I meant bug 344802... (In reply to Peter Maydell from comment #1) > Looks like the same as bug 344082 to me (insn is reading CNTVCT). That bug seems unrelated to valgrind. (In reply to Peter Maydell from comment #2) > Doh, I meant bug 344802... that makes more sense now :D *** This bug has been marked as a duplicate of bug 344802 *** |
disInstr(arm): unhandled instruction: 0xEC510F1E cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE) ==13274== valgrind: Unrecognised instruction at address 0x507b468. ==13274== at 0x507B468: _armv7_tick (armv4cpuid.S:94) ==13274== Your program just tried to execute an instruction that Valgrind ==13274== did not recognise. There are two possible reasons for this. ==13274== 1. Your program has a bug and erroneously jumped to a non-code ==13274== location. If you are running Memcheck and you just saw a ==13274== warning about a bad jump, it's probably your program's fault. ==13274== 2. The instruction is legitimate but Valgrind doesn't handle it, ==13274== i.e. it's Valgrind's fault. If you think this is the case or ==13274== you are not sure, please let us know and we'll try to fix it. ==13274== Either way, Valgrind will now raise a SIGILL signal which will ==13274== probably kill your program.