Talk:C dynamic memory allocation/Archive 2: Difference between revisions

Revision as of 00:56, 2 June 2016

Latest revision as of 01:22, 5 October 2023

(3 intermediate revisions by the same user not shown)

Line 74:

*'''Comment.''' In case anyone's curious to see them, here are some links to archival snapshots of malloc at [http://minnie.tuhs.org/cgi-bin/utree.pl The Unix Tree]. The earliest I could find was dmr's [http://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/dmr/malloc.c Fourth Edition malloc.c], dated 8-31-1973. The [http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/malloc.c PWB1 malloc.c], dated 2-10-1980, implemented the whole memory allocator, including free, but realloc was separately compiled as [http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/realloc.c realloc.c], so that if you didn't actually need those bytes of code, they wouldn't be linked in. In the [http://minnie.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/lib/libc/vax/gen/malloc.c System III malloc.c], dated 4-11-1980, and the [http://minnie.tuhs.org/cgi-bin/utree.pl?file=Ultrix-3.1/src/libc/gen/malloc.c Ultrix 3.1 malloc.c], dated 4-22-1986, realloc is part of malloc.c. You can compare those mallocs to the [http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD/usr/src/lib/libc/gen/malloc.c BSD4.3 malloc.c], dated 3-9-1986. The BSD malloc does not do coalescing; instead, it just uses a small number of lists of fixed sized blocks (analogous to the strategy I mentioned PL/I programmers used to use.) The Bell Labs mallocs all did coalescing. [[User:Msnicki|Msnicki]] ([[User talk:Msnicki|talk]]) 17:57, 30 October 2011 (UTC)

==Move discussion in progress==

There is a move discussion in progress which affects this page. Please participate at [[Talk:C standard library#Move request through WP:RM|Talk:C standard library - Requested move]] and not in this talk page section. Thank you. <!-- Talk:C standard library crosspost --> —[[User:RM bot|RM bot]] 09:40, 8 November 2011 (UTC)

== Can we take the "not casting is important because you might have not included stdlib.h" argument... ==

out behind the woodshed and shoot it please? Every time I see it (not just on Wikipedia) I want to slap someone. - [[User:Richfife|Richfife]] ([[User talk:Richfife|talk]]) 08:02, 30 January 2013 (UTC)

== reallocarray ==

We should probably have a mention of [[OpenBSD]]'s relatively recent <code>[[reallocarray]]</code>[http://www.openbsd.org/cgi-bin/man.cgi?query=reallocarray] interface here, too, but I'm not an expert on the history of and variations between the various C library versions, so I'm not the best person to add this to the article. -- [[User:The Anome|The Anome]] ([[User talk:The Anome|talk]]) 09:04, 21 October 2014 (UTC)

== segmentation fault ==

"usually causes a segmentation fault" sounds like a PDP-11 or UNIX term. It will be called other things on other machines and OSs. Like Memory Access Violation. In embedded systems, it may not cause a trap at all.

But expect a program crash.

[[User:Wmdgus73|Wmdgus73]] ([[User talk:Wmdgus73|talk]]) 19:55, 28 May 2015 (UTC)