We are creating a CPU test for our hardware and are running the following
snipet of code:
while (!done) count++;
done is an int that is set inside an alarm handler.
count is an unsigned long and never approaches overflow.
Basically, we set an alarm and then see how many times it ticks (count).
We are getting a SIGILL on a particualr device and are deeming this to be
a hardware concern as the program runs fine on the same platform on other
nodes.
Any thoughts?
Have you run the program in the debugger to get an idea of where the SIGILL
is coming from? More than likely it is a hardware issue if you can run the
same binary on multiple machines of the same hardware.
–
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Doug Rixmann” <rixmannd@rdsdata.com> wrote in message
news:a21jen$jvd$1@inn.qnx.com…
We are creating a CPU test for our hardware and are running the following
snipet of code:while (!done) count++;
done is an int that is set inside an alarm handler.
count is an unsigned long and never approaches overflow.
Basically, we set an alarm and then see how many times it ticks (count).
We are getting a SIGILL on a particualr device and are deeming this to be
a hardware concern as the program runs fine on the same platform on other
nodes.Any thoughts?