[Valgrind-users] unhandled opcodes with ioport

[Rupert K. <rk...@mu...>]

Hello everybody,

I just found out that valgrind chokes when trying to access ioports via
inb() or outb(). It complains about unhandled opcodes.

I have attached a short demo code, as well as output from test runs on
my system. I compiled it with gcc 2.95.3 without any options.

Unfortunately, I do know enough about valgrind (and assembler...) to
implement this myself. Probably, some modifications will be necessary to
treat ioports as defined memory even if they have not been written.

Anyone with the necessary skills wants to jump in?

thanks,

Rupert

PS: BIG THANKS to all contributors to this great tool!