|
From: <woo...@co...> - 2005-01-19 05:50:02
|
In attempting to use valgrind against the TOCNET32 program,
the following
error occurs:
==1533==
disInstr: unhandled instruction bytes: 0xFA 0x83 0xEC 0x8
at 0x8094F1F: Dsp2187::DataMemRead(unsigned
short, unsigned short,
int, unsigned short *) (./source/dsp2187.cpp:444)
==1533==
==1533== Process terminating with default action of signal
4 (SIGILL)
==1533== Illegal operand at address 0xB0022670
==1533== at 0x8094F1F: Dsp2187::DataMemRead(unsigned
short, unsigned short,
int, unsigned short *) (./source/dsp2187.cpp:444)
==1533== by 0x8095CCC: Dsp2187::ChkWdTimer(void)
(./source/dsp2187.cpp:982)
==1533== by 0x80947E1: Dsp2187::Dsp2187(unsigned short,
unsigned short,
char) (./source/dsp2187.cpp:133)
==1533== by 0x80F60D9: TocSystem::TocSystem(void)
(./source/tocsys.cpp:843)
==1533==
The error is believed to be caused by writing to an output
address. This is
allowed to root when properly registered with the kernel
(which it is). Is it
possible to disable this type of error message or have
valgrind accept the
same registration?
|
|
From: Tom H. <th...@cy...> - 2005-01-19 08:38:14
|
In message <200...@sm...>
woo...@co... wrote:
> The error is believed to be caused by writing to an output
> address. This is allowed to root when properly registered with the
> kernel (which it is). Is it possible to disable this type of error
> message or have valgrind accept the same registration?
It isn't a question of disabling any message - your program is
using an instruction which valgrind doesn't understand. Please
file a bug so that we can look at adding support for this instruction.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|