News for hackers. Stuff that matters.
Re:What Every C Programmer Should Know About Undefined Behav... by nnhtzgf on Tuesday January 13, 2015 @04:20AM (#8878797)
The title is making it seem as the listed behavior is largely unknown to C programmers. It isn't. And it is in the manual.
Re:What Every C Programmer Should Know About Undefined Behav... by ape4 on Tuesday January 13, 2015 @04:22AM (#8878802)
Yeah, hopefully if you are programming in C you'll know using an undefined variable is bad.
Re:What Every C Programmer Should Know About Undefined Behav... by nnhtzgf on Tuesday January 13, 2015 @04:25AM (#8878807)
Yep. :-)

The article doesn't make much sense at times: Dereferencing a NULL Pointer: >>>contrary to popular belief<<<, dereferencing a null pointer in C is undefined.

I guess C programmers are not counted in the "popular" group.

Re:What Every C Programmer Should Know About Undefined Behav... by stormbrew on Tuesday January 13, 2015 @04:32AM (#8878825)
I don't think it's wrong at all. I suspect if you asked a large number of even moderately competent C programmers, you'd find quite a lot of them believe it's defined to trap. That's exactly what the rest of it is talking about. Never mind the issue raised of how it potentially affects optimization, which I think very few C programmers would actually be able to speak to.
Re:What Every C Programmer Should Know About Undefined Behav... by bhaak on Tuesday January 13, 2015 @04:33AM (#8878828)
Are you really sure that most C programmers know about this?

IMO, if you'd ask the question "what happens if you dereference a NULL pointer", most C programmers would answer "a segfault".

Re:What Every C Programmer Should Know About Undefined Behav... by unwind on Tuesday January 13, 2015 @06:15AM (#8879087)
That, of course, would be a leading question. Most people would probably tend to assume that you're asking "in the environment in which we're programming, what happens if you dereference NULL?" which is not what you meant.

I didn't poll my coworkers either, but at least I think the answers would be different if I asked "what does C say should happen when a NULL pointer is dereferenced?".

Perhaps that's just wishful thinking on my behalf, though. :)

Re:What Every C Programmer Should Know About Undefined Behav... by ghswa on Tuesday January 13, 2015 @07:31AM (#8879330)
I don't think that's particularly wishful thinking, however, your alternative phrasing could be seen as equally, if not more, leading.

When quizzed on the behaviour of a C program I would expect a careful and experienced C programmer to consider the behaviour described by the standard (which standard?); unspecified and implementation defined behaviours; and deviations from the standard in both the compiler and the environment. Often I'd expect the answer to be "it depends".

Re:What Every C Programmer Should Know About Undefined Behav... by Retra on Tuesday January 13, 2015 @03:27PM (#8882363)
I think, once you unanimously conclude that something should not be done, that people don't really care _why_ it shouldn't be done until someone tries to suggest you should do it.

For example, we know not to dereference null pointers. It is pretty much never correct to do so, and it's hard to imagine otherwise. What does it matter what C says should happen when you do it? You're never going to intentionally do it, so it becomes an incongruous hypothetical. Like "what would happen if you were never born?" The answer is useless because the question is inherently flawed.

Re:What Every C Programmer Should Know About Undefined Behav... by OneOneOneOne on Tuesday January 13, 2015 @11:04AM (#8880626)
Good point. Some embedded environments will have different behavior. I don't recall what happened under MS DOS or if MS compiler provided an debug option.
Re:What Every C Programmer Should Know About Undefined Behav... by mikeash on Tuesday January 13, 2015 @08:45AM (#8879719)
Clang, for example, will optimize out some NULL dereferences. So even in real environments that people use, "it segfaults" is wrong.

Edit: some NULL dereferences.

Re:What Every C Programmer Should Know About Undefined Behav... by calrogman on Tuesday January 13, 2015 @10:43AM (#8880482)
In that case the machine code generated doesn't dereference NULL, so the answer "it segfaults" isn't wrong.
Re:What Every C Programmer Should Know About Undefined Behav... by heinrich5991 on Tuesday January 13, 2015 @11:28AM (#8880788)
In the C code, a null pointer is dereferenced. A segfault is not happening in the executable. Arguing about intermediate steps is kinda moot IMO.
Re:What Every C Programmer Should Know About Undefined Behav... by mikeash on Tuesday January 13, 2015 @11:46AM (#8880911)
The very concept of dereferencing doesn't exist at that level.
Re:What Every C Programmer Should Know About Undefined Behav... by mikeash on Wednesday January 14, 2015 @10:53AM (#8886974)
I'll take the downvote as a request for elaboration. In C, you dereference a pointer. This typically translates to machine code that loads memory at an address. The translation is so direct that we tend to think of them as identical, i.e. dereferencing a pointer is loading memory at an address. But this is not so; first of all, nothing says pointers have to be implemented as memory addresses in the first place, and even if you do implement them that way (as virtually every C implementation does), not every pointer dereference has to generate a load instruction. That's not just the case for optimizing out NULL dereferences. Optimizations mean that in general, an expression p can have the memory load optimized away if the value at that location is already known from a previous computation (say, because you just assigned a value there, or you read the value a bit earlier and it's still available in a register).

In C, you deference a pointer. In assembly or machine code, you load memory at an address. The two don't have to happen at the same time, though, and just because you don't end up loading memory at an address doesn't mean you didn't dereference a pointer.

In short:

    *(char *)NULL
This always dereferences NULL, even if the compiler optimizes out the statement entirely.
Re:What Every C Programmer Should Know About Undefined Behav... by nnhtzgf on Tuesday January 13, 2015 @04:46AM (#8878846)
If you are in a company that codes largely in C, do a pool and report back. I'm honestly curious.
Re:What Every C Programmer Should Know About Undefined Behav... by bhaak on Tuesday January 13, 2015 @05:41AM (#8878978)
Unfortunately, I don't work in such a company.

A completely unrepresentative poll among two C++ programmers showed that 50% thought it was a segfault, whereas the other 50% suggested it could be undefined behavior, deducing that from the knowledge that the behavior is different in Linux userspace and kernel.

Although I wouldn't call those two typical C++ programmers. They do security CTFs for fun, so they might have a broader knowledge about exploitable behaviors in C/C++ code.

Re:What Every C Programmer Should Know About Undefined Behav... by legulere on Tuesday January 13, 2015 @05:49AM (#8879006)
For a while you were actually able to mmap the memory at address NULL under linux, which is usable for exploiting (you can pass arbitrary data to kernel code that you can bring to dereference null pointers)
Re:What Every C Programmer Should Know About Undefined Behav... by orbifold on Tuesday January 13, 2015 @10:46AM (#8880501)
Wouldn't virtual address translation prevent this from happening?