Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

75%
+4 −0
Q&A Is partial allocation of an object Undefined Behavior?

Since I don't think the C standard says anything explicitly about cases like this, it is probably undefined behavior, under the "not mentioned in the standard" variety. If something isn't mentioned...

posted 2y ago by Lundin‭

Answer
#1: Initial revision by user avatar Lundin‭ · 2023-01-23T11:00:49Z (almost 2 years ago)
Since I don't think the C standard says anything explicitly about cases like this, it is probably undefined behavior, under the "not mentioned in the standard" variety. If something isn't mentioned, it is per definition undefined and not well-defined.

The closest thing might be the somewhat unclear rules about "effective type" and "strict aliasing" in 6.5: "For all other accesses to an object having no declared type, the effective type of the object is simply the type of the lvalue used for the access." Everything returned from `malloc` has no declared type. 

This doesn't mention anything about arrays, except that we can make an access through an "aggregate" (array or struct) that contains the effective type as one of its members.

However, nothing in the standard mentions what happens when you allocate too little space. As far as `malloc` is concerned, you have allocated an object with size `50 * sizeof(int)` bytes, which has no declared type.