No description

Khaïs COLIN 82da182773 fix: potential buffer overflow caused by missing terminating null byte in t_buffer ... This only occurs in specific circumstances where the number of bytes to be added to a t_buffer via the ft_buffer_push_buf function is exactly equal to the number of free bytes in the current underlying buffer. This does not occur if the number of bytes to add to the buffer is smaller than that, since we allocate new space using ft_calloc. In these circumstances, since no terminating null byte is added, other code may read past the end of the buffer, causing a buffer overflow.		2025-04-15 15:17:51 +02:00
libft	debug: remove *alloc/free debug information	2025-03-10 13:22:29 +00:00
src	fix: potential buffer overflow caused by missing terminating null byte in t_buffer	2025-04-15 15:17:51 +02:00
tests	debug: worddesc show more information	2025-04-15 15:17:51 +02:00
.gitignore	tests: implement a better integration test framework than shellspec	2025-03-28 14:50:37 +01:00
.valgrindrc	valgrind: suppress readline still reachable leaks	2025-02-07 15:29:43 +01:00
grammar.md	parse-cmd: Almost done but stopped by the gong	2025-04-08 19:56:46 +02:00
interesting_tests.md	Expansion : text replacement in a string	2025-03-21 10:04:25 +01:00
Makefile	token_type: assign token_type to worddesc during wordsplit	2025-04-15 15:17:51 +02:00
NOTES.md	cmdlist: use new architecture (STUB)	2025-03-28 14:50:37 +01:00
readline.supp	leaks: ignore readline add_history leaks	2025-03-28 14:50:37 +01:00
test.sh	token_type: assign token_type to worddesc during wordsplit	2025-04-15 15:17:51 +02:00