The C language in the planet Mars

[jacob navia]

Mankind has now two robots wandering about in the planet Mars. No,
it wasn't Mars that invaded Earth, but Earth that landed in Mars
more than two years ago.

After some initial OS glitches (Chris Torek can comment
on those probably) in the Spirit robot, software has done
smoothly ever since.

All the software is written in C, what is a good decision
but also a bad one, C with its warts and all...

In the last two weeks, a software upgrade was sent from
earth to Mars, and the upgrade is scheduled to be
tested this days. Software upgrades take a lot of time
when they are done with several million kilometers
distance!

The Mars Exploration Rover software (MER) is around
650 000 lines of C. The Ames research center developed a
static tester for the software [2] and in 30 minutes
it discovered...

o Un-initialized variable usage
o Returning the address of a local variable (!!!!)
o Overflow in constant expression.

I wonder what kind of compilers does the VXWorks system
use, but almost all compilers I know of will try to
diagnose this kind of errors...

In a news item published in Space daily [1], Green Hills software
boasted that
< quote >
"Green Hills Software Tools Critical To Mars Rover Missions"

Both the "Opportunit y" rover, launched July 7, and the "Spirit" rover,
launched June 10, are being directed and controlled by software programs
and systems written with the use of Green Hills development tools.

< end quote >

Green Hills doesn't emit a diagnostic for returning the address of
a local variable?
References:
[1]
http://www.marsdaily.com/reports/Gre..._Missions.html
[2]
http://ic.arc.nasa.gov/researchinfus...S/SMC-IT03.pdf

[Richard Tobin]

In article <44************ *********@news. orange.fr>,
jacob navia <ja***@jacob.re mcomp.frwrote:

>o Returning the address of a local variable (!!!!)

>Green Hills doesn't emit a diagnostic for returning the address of
a local variable?

I don't know the details of this particular case, but suppose the
code was something like this:

int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;
}

How many compilers produce a warning for that?

-- Richard

[jacob navia]

Richard Tobin a écrit :

In article <44************ *********@news. orange.fr>,
jacob navia <ja***@jacob.re mcomp.frwrote:

>>o Returning the address of a local variable (!!!!)

>>Green Hills doesn't emit a diagnostic for returning the address of
a local variable?

I don't know the details of this particular case, but suppose the
code was something like this:

int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;
}

How many compilers produce a warning for that?

-- Richard

Yes, you are right. That would be much more
difficult to find. The other errors are maybe
easier: const overflow can be detected at
compile time.

[Nils Weller]

On 2006-07-23, jacob navia <ja***@jacob.re mcomp.frwrote:

Richard Tobin a écrit :

>In article <44************ *********@news. orange.fr>,
jacob navia <ja***@jacob.re mcomp.frwrote:

>>>o Returning the address of a local variable (!!!!)

>>>Green Hills doesn't emit a diagnostic for returning the address of
a local variable?

I don't know the details of this particular case, but suppose the
code was something like this:

int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;
}

How many compilers produce a warning for that?

-- Richard

Yes, you are right. That would be much more
difficult to find.

Hmm, maybe it would be feasible to make this a runtime error. With a
typical stack frame layout, the compiler can easily check whether
returned (non-null) pointer values point into the frame, and if that's
the case terminate the process or call a user-defined error handler or
somesuch.

Probably not worth the cost in general, but could come in handy during
development/debugging.

--
Nils R. Weller, Bremen (Germany)
My real email address is ``nils<at>gnuli nux<dot>nl''
.... but I'm not speaking for the Software Libre Foundation!

[spibou]

Richard Tobin wrote:

In article <44************ *********@news. orange.fr>,
jacob navia <ja***@jacob.re mcomp.frwrote:

o Returning the address of a local variable (!!!!)

Green Hills doesn't emit a diagnostic for returning the address of
a local variable?

I don't know the details of this particular case, but suppose the
code was something like this:

int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;
}

How many compilers produce a warning for that?

I decided to do a little experiment with the programme below.

int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;

}

int main() {

return 0 ;
}

The Sun compiler , lint on Solaris and gcc -Wall did not
produce any warnings. But splint gave

o.c:8:12: Stack-allocated storage pointer reachable from return value:
pointer
A stack reference is pointed to by an external reference when the
function
returns. The stack-allocated storage is destroyed after the call,
leaving a
dangling reference. (Use -stackref to inhibit warning)
Spiros Bousbouras

[BubbaGump]

On Sun, 23 Jul 2006 10:44:43 +0200, jacob navia
<ja***@jacob.re mcomp.frwrote:

>Mankind has now two robots wandering about in the planet Mars. No,
it wasn't Mars that invaded Earth, but Earth that landed in Mars
more than two years ago.

After some initial OS glitches (Chris Torek can comment
on those probably) in the Spirit robot, software has done
smoothly ever since.

All the software is written in C, what is a good decision
but also a bad one, C with its warts and all...

Maybe the problem's with the people writing the language as much as it
is with the language itself. French isn't a bad language just because
monkey's can't speak it.

C is good for anal retentive people who catch most of their own
mistakes. It's apparently not good for normal people.

[Richard Heathfield]

BubbaGump said:

<snip>

>
C is good for anal retentive people who catch most of their own
mistakes.

Are you a qualified psychiatrist, using that term in its medical sense? If
so, please provide evidence to support this.

Or are you just an irksome little jerk who is trying to offend people?

It's apparently not good for normal people.

C is fine for normal people who know how to think. If you don't know how to
think, stay away not just from C, but from programming.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)

[Ham]

sp****@gmail.co m wrote:

>
int *foo(void)
{
int local;
int *pointer;

pointer = &local;

return pointer;

}

int main() {

return 0 ;
}

PC-LINT produces the following warning for that piece of code:

diy.c 11 Warning 674: Returning address of auto through
variable 'pointer'.

This example is also a sample violation of MISRA C:2004

[Walter Roberson]

In article <D9************ ********@bt.com >,
Richard Heathfield <in*****@invali d.invalidwrote:

>BubbaGump said:

>C [...]

>It's apparently not good for normal people.

>C is fine for normal people who know how to think.

There are compelling claims that programmers are not normal people ;-)
--
If you lie to the compiler, it will get its revenge. -- Henry Spencer

[Tak-Shing Chan]

On Tue, 25 Jul 2006, Walter Roberson wrote:

In article <D9************ ********@bt.com >,
Richard Heathfield <in*****@invali d.invalidwrote:

>BubbaGump said:

>>C [...]

>>It's apparently not good for normal people.

>C is fine for normal people who know how to think.

There are compelling claims that programmers are not normal people ;-)

Indeed. A week or so ago, someone on comp.lang.c wrote,
``Neither is anyone. Normality is a myth. (Do the math. How many
people are normal in every respect?)'' (attribution withheld).

Tak-Shing