[Issue 11788] New: [x86] Valgrind unhandled instruction bytes: 0xC8 0x8 0x0 0x0
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Sat Dec 21 06:33:27 PST 2013
https://d.puremagic.com/issues/show_bug.cgi?id=11788
Summary: [x86] Valgrind unhandled instruction bytes: 0xC8 0x8
0x0 0x0
Product: D
Version: D2
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: DMD
AssignedTo: nobody at puremagic.com
ReportedBy: bruno.deligny at gmail.com
--- Comment #0 from Bruno Deligny <bruno.deligny at gmail.com> 2013-12-21 06:33:22 PST ---
I have this error with valgrind with an very simple 32 bits exe generated with
dmd.
import std.stdio;
int main()
{
writeln("Hello world");
return 0;
}
dmd -g main.d
==7091== Memcheck, a memory error detector
==7091== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==7091== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==7091== Command: ./main
==7091==
vex x86->IR: unhandled instruction bytes: 0xC8 0x8 0x0 0x0
==7091== valgrind: Unrecognised instruction at address 0x8069b54.
==7091== at 0x8069B54: ??? (in /home/bruno/main)
==7091== Your program just tried to execute an instruction that Valgrind
==7091== did not recognise. There are two possible reasons for this.
==7091== 1. Your program has a bug and erroneously jumped to a non-code
==7091== location. If you are running Memcheck and you just saw a
==7091== warning about a bad jump, it's probably your program's fault.
==7091== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7091== i.e. it's Valgrind's fault. If you think this is the case or
==7091== you are not sure, please let us know and we'll try to fix it.
==7091== Either way, Valgrind will now raise a SIGILL signal which will
==7091== probably kill your program.
==7091==
==7091== Process terminating with default action of signal 4 (SIGILL)
==7091== Illegal opcode at address 0x8069B54
==7091== at 0x8069B54: ??? (in /home/bruno/main)
==7091==
==7091== HEAP SUMMARY:
==7091== in use at exit: 0 bytes in 0 blocks
==7091== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==7091==
==7091== All heap blocks were freed -- no leaks are possible
==7091==
==7091== For counts of detected and suppressed errors, rerun with: -v
==7091== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Instruction non permise
--
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
More information about the Digitalmars-d-bugs
mailing list