ANSI C code testing

[praveen]

Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

[Ian Collins]

praveen wrote:

Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

Unit tests?

--
Ian Collins.

[Micah Cowan]

praveen wrote:

Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

Ian Collins gave the most correct answer. The number of potential kinds
of runtime errors are infinite. Some kinds can certainly be discovered
programatically, some can't. Some can be determined by examining the
source code, some can't. Errors in logic, for instance, are runtime
errors, and yet completely impossible to catch automatically in some
general way. These, especially, benefit from the use of unit tests.

Memory abuse is a common runtime error, and fortunately there are many
tools available for at least /helping/ to catch these. Tools like
Valgrind or Electric Fence will help here.

A good "lint" program can also be very useful for this sort of thing.

[jacob navia]

praveen a écrit :

Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

You can run your code in the 8051 emulator
http://sourceforge.net/projects/emu51/

[Malcolm]

"Micah Cowan" <mi***@cowan.namewrote in

praveen wrote:

>Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

Ian Collins gave the most correct answer. The number of potential kinds
of runtime errors are infinite. Some kinds can certainly be discovered
programatically, some can't. Some can be determined by examining the
source code, some can't. Errors in logic, for instance, are runtime
errors, and yet completely impossible to catch automatically in some
general way. These, especially, benefit from the use of unit tests.

Memory abuse is a common runtime error, and fortunately there are many
tools available for at least /helping/ to catch these. Tools like
Valgrind or Electric Fence will help here.

A good "lint" program can also be very useful for this sort of thing.

The snag is that embedded code that interacts with hardware is difficult to
unit test, except in an emulator, and an emulator is as hard to write as the
actual program.

Separate out the IO from the the logic, or as I put it, the procedures from
the functions. The logic can be unit tested. The IO will probaly need
testing on hardware.
--
www.personal.leeds.ac.uk/~bgy1mm
freeware games to download.

[jacob navia]

Malcolm a écrit :

"Micah Cowan" <mi***@cowan.namewrote in

>>praveen wrote:

>>>Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

Ian Collins gave the most correct answer. The number of potential kinds
of runtime errors are infinite. Some kinds can certainly be discovered
programatically, some can't. Some can be determined by examining the
source code, some can't. Errors in logic, for instance, are runtime
errors, and yet completely impossible to catch automatically in some
general way. These, especially, benefit from the use of unit tests.

Memory abuse is a common runtime error, and fortunately there are many
tools available for at least /helping/ to catch these. Tools like
Valgrind or Electric Fence will help here.

A good "lint" program can also be very useful for this sort of thing.

The snag is that embedded code that interacts with hardware is difficult to
unit test, except in an emulator, and an emulator is as hard to write as the
actual program.

But there is an emulator for the 8051 ALREADY written,
as I pointed out in my answer.

The "expanded" version of that minuscule chip has 256
BYTES of RAM...

With so few bytes available even a "brute force" approach
to testing could work...

Separate out the IO from the the logic, or as I put it, the procedures from
the functions. The logic can be unit tested. The IO will probaly need
testing on hardware.

[Ian Collins]

Malcolm wrote:

"Micah Cowan" <mi***@cowan.namewrote in

>>praveen wrote:

>>>Hi,

I am writing c code for ATMEL 8051 core in ANSI c. we are using KEIL
compiler for it. I want to test my c code and improve my programming
skills. Can any one suggest the software tool that can test my c code
for runtime errors?

Ian Collins gave the most correct answer. The number of potential kinds
of runtime errors are infinite. Some kinds can certainly be discovered
programatically, some can't. Some can be determined by examining the
source code, some can't. Errors in logic, for instance, are runtime
errors, and yet completely impossible to catch automatically in some
general way. These, especially, benefit from the use of unit tests.

Memory abuse is a common runtime error, and fortunately there are many
tools available for at least /helping/ to catch these. Tools like
Valgrind or Electric Fence will help here.

A good "lint" program can also be very useful for this sort of thing.

The snag is that embedded code that interacts with hardware is difficult to
unit test, except in an emulator, and an emulator is as hard to write as the
actual program.

But often way more fun!

>
Separate out the IO from the the logic, or as I put it, the procedures from
the functions. The logic can be unit tested. The IO will probaly need
testing on hardware.

Agreed, assuming you neither have nor want to write an emulation.

--
Ian Collins.