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 »

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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post almost 3 years ago by Monica Cellio‭.

54 / 255
  • What is `malloc`'s standard-defined behavior with respect to the amount of memory it allocates?
  • What is malloc's standard-defined behavior with respect to the amount of memory it allocates?
I recently told a friend that `malloc(n)` allocates and returns a pointer to a block of *at least N* bytes of memory, as opposed to *exactly N*; that it is allowed to allocate 'extra' memory to meet e.g. alignment requirements.

He asked what the C standard had to say about this behaviour. I wasn't sure, so I looked it up, and...I can't find any explicit statement on the subject.

Did I miss something in the standard, or was I wrong to begin with? What is `malloc`'s standard-defined behaviour with respect to the block of memory it returns?

(this discussion was in the context of a single-byte buffer-overrun bug that only manifested when N was a multiple of 8; it certainly *looked* like malloc was rounding up to the word size, although obviously trying to use any such slop is still a bug)

Suggested almost 3 years ago by hkotsubo‭