|
From: Gabriel G. <go...@co...> - 2003-09-04 18:11:46
|
Dear Valgrind Team:
We're using Valgrind to debug a system. I must tell that it's great
software! It's a great tool for finding memory leaks and other memory
errors such as invalid reads & writes.
We've been using it flawlessly until we found two illegal instruction
errors in valgrind log and our system dies with "Illegal instruction"
message.
1) disInstr: unhandled instruction bytes: 0xEE 0xC9 0xC3 0x55
2) disInstr: unhandled instruction bytes: 0xEC 0x88 0x45 0xFC
I've been searching in Intel Instruction set reference for x86 and it
tells that:
a) 0xEE is OUT I/O instruction
b) 0xEC is IN I/O instruction
1) We're using framebuffer in our system and writing directly to vga
registers with an outb C function (previous call to ioperm) and I think
it dies there.
2) We're using inb C function (previous call to ioperm) to control a
cash drawer on i/o port 0x101.
Our system works perfectly without valgrind, but we are eager to keep
debugging it and this problem is stopping our task. :(
So the question is:
Are this instructions supported in valgrind? If not, is there a complex
technical problem in implementing them? Do you have any pointers to docs
if I decide to give you a hand and implementing them?
Thanks for your time, and keep up this very good software!
PD: Please CC me any replies, cause I'm not subscribed to the list.
--
.^. Gabriel Gomiz - Red Hat Certified Engineer (RHCE)
/V\ Gerencia de Sistemas - Cooperativa Obrera Ltda.
// \\ Tel (0291) 456-0084
/( )\
^^-^^ s/Window[$s]/LINUX!!/g or die;
|