| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | This commit was manufactured by cvs2git to create tag 'tb_20250802'.tb_20250802 | cvs2svn | 2025-08-02 | 2 | -331/+0 |
| | | |||||
| * | Adapt test to new malloc_options regime | otto | 2025-05-24 | 1 | -7/+8 |
| | | |||||
| * | t22 and t23 can fail if the first chunk ends up being allocated at | otto | 2024-04-14 | 1 | -2/+12 |
| | | | | | | the very end of the page. Circumvent that. Reported by and fix ok anton@ | ||||
| * | A few more tests | otto | 2023-10-22 | 1 | -1/+15 |
| | | |||||
| * | More thorough write-afetr-free checks. | otto | 2023-06-04 | 1 | -6/+21 |
| | | | | | | | | | | | | | | | | | | | | On free, chunks (the pieces of a pages used for smaller allocations) are junked and then validated after they leave the delayed free list. So after free, a chunk always contains junk bytes. This means that if we start with the right contents for a new page of chunks, we can *validate* instead of *write* junk bytes when (re)-using a chunk. With this, we can detect write-after-free when a chunk is recycled, not justy when a chunk is in the delayed free list. We do a little bit more work on initial allocation of a page of chunks and when re-using (as we validate now even on junk level 1). Also: some extra consistency checks for recallocaray(3) and fixes in error messages to make them more consistent, with man page bits. Plus regress additions. | ||||
| * | Make malloc tests that set flags more robust against the user also | otto | 2023-05-09 | 1 | -2/+2 |
| | | | | | having flags set. | ||||
| * | Add a regress test to test various malloc API and heap mismanagement | otto | 2023-05-08 | 2 | -0/+291 |
| errors which should cause abort. A few are not enabled yet, they will be once the corresponding diffs in malloc are committed. | |||||
