有人可以解释malloc（）吗？

特别是XC32的实现，因为我知道它们都是不同的。我了解MalCube（）做什么：你要求X字节，它返回一个指向那个内存段开始的指针。但是如果我使用了一个带有200K堆的部件，并且说我是MalCube（）50K，然后是100K……那么，我将（50k）（和）重新分配到另一个90K？有东西告诉我，这将失败，因为我怀疑任何东西都在后台移动。我以前从未在嵌入式系统上使用过MalCube（），因为它不是100%的效率，而是我自己制作的非常粗糙的系统，在那里我必须以反顺序的顺序释放任何分配的块。阳离子。这是棘手的，因为它需要大量的调试。但是现在我在设计一个带有大量RAM的PIC32 MZ，我不关心一些浪费（这就是我们如何使用PC，我知道）。当使用MalCube（）来分配稍后将被释放的大块RAM时，有哪些最佳实践？分配顺序需要考虑吗？



      以下为原文

    ....especially the XC32 implementation since I understand they are all different?

I understand what malloc() does: you ask for x bytes and it returns a pointer to the start of that memory section. But what happens if I am using a part with 200K heap and say I malloc() 50K, then 100K....then I free() the 50K and attempt to malloc() another 90K? Something tells me this will fail because I doubt anything is getting moved around in the background.

I've never used malloc() on an embedded system before because it's not 100% efficient, but rather I made my own very crude system where I'd have to free any allocated chunks in reverse order of allocation. This was touchy though as it required a lot of debugging. But now I'm looking at designing with a PIC32MZ with so much RAM I don't care about some waste (and that's how we got to where we are with the PC, I know).

What are some best practices when using malloc() to allocate large chunks of RAM that will be freed at a later time? Is order of allocation something to consider?