Re: [PATCH] Nano-malloc: Fix for unwanted external heap fragmentation
Keith Packard <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <[email protected]> |
Ola Olsson <[email protected]> writes: > Now when I skimmed through the code I couldn't find anything regarding the > API robustness. > Do you think you can point me in the right direction? Allocations of very large or negative amounts now fail appropriately; there were a few corner cases which did the wrong thing before. Oh, I also changed the behavior of 'malloc' to always set memory to zero; that makes the system more consistent in that application failures to initialize memory now always get the same result. It's a bit slower, but I feel like the added layer of reliability is worth it. -- -keith
signature.asc
(application/pgp-signature, 832 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmCLLoMACgkQ2yIaaQAA ABFbJBAAmErvcVvFB7gDarK2WiGubV5uL24jAM1J8SJNub1x4R4Jux574trA2FtL iXqvErKquKMKc7NlJEvqR1rqfg48NhfprdhzgG6llr9IuJQCRZwax7mw2tlDDhmq LsCUZtZqSY7NqmpCEtlrH4EtSa6EQOPluPbEAK7XC5INNgI2bcAwfFxxubNrzx5j Hva+pTCu2TenC57PNU6yXAniUABI3cyulEexRs0d9OaEh82H7v3rq3Y0VUx3LCe8 /AgvmPt7m8loIQtBA7YSlcV2+bglg263RnNJ0B4OcXJ9N+WhE6XPMTBJbAdG/zvS XKr+v74jegtfeA0uWQqORlOiw8YHvU6hpjFmODls+HSj7qXNTkGRskFOM7iFcitz IkFF5lryNAhjKqKEu9n6UEdAnp0PPoMksfHPZ5YMU1x743ysXoFVvIwIuP1USXl4 se4SfsnbFj0MLMDjgCpKqotnp3zfY6t0qVtjvWxrAbdRw/fADcEbF4M2JTjplWDY FCYc7W5Ck4drIbFX80Ih1OhcmIqZZXoCaRwqDhdhED2NuBGXZxtCjCsSdIjVN8es dOWVndmiGb7hRqGKpMRT3FrHpU9HJQtFL2SXTOc7J5AkjaQ/gYNTg4C7pGqfjOO7 lJfJlpIqA6jLzr5/uasdmAk79etdl5KA8YZ7aU73dJtZguwKiJI= =64Hs -----END PGP SIGNATURE-----