[Bug 259294] [libc] add a freeres function

2024-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 Paul Floyd changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 259294] [libc] add a freeres function

2022-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #8 from Paul Floyd --- (In reply to Paul Floyd from comment #6) Quick confirmation: =5018== 2,048 bytes in 1 blocks are still reachable in loss record 1 of 2 ==5018==at 0x484CBC4: malloc (vg_replace_malloc.c:397) ==5018==

[Bug 259294] [libc] add a freeres function

2022-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 Brooks Davis changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #7 f

[Bug 259294] [libc] add a freeres function

2022-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #6 from Paul Floyd --- Another function to add to the list (not tested, just from looking at the code): setproctitle_internal has 2 static pointers that get malloc'd and never freed. -- You are receiving this mail because: You

[Bug 259294] [libc] add a freeres function

2022-04-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #5 from Paul Floyd --- (In reply to Mark Johnston from comment #4) I guess there are probably several other things that would need freeing. GNU libc looks like it calls about 5 functions from __libc_freeres: IO, dl, thread, an

[Bug 259294] [libc] add a freeres function

2022-04-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #4 from Mark Johnston --- Presumably there are many other places in libc that need to be hooked. For instance, any use of getgrent(3) will trigger allocation of a global buffer, no? -- You are receiving this mail because: You

[Bug 259294] [libc] add a freeres function

2022-04-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 Li-Wen Hsu changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 259294] [libc] add a freeres function

2021-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #3 from Paul Floyd --- Created attachment 229927 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229927&action=edit __libc_freeres Initial prototype. makebuf is where the memory for stdout gets allocated, so I put fre

[Bug 259294] [libc] add a freeres function

2021-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #2 from Paul Floyd --- With a debug build of libc, if I run a canonical C 'printf hello world' as follows LD_PRELOAD=/home/paulf/build/src/obj/usr/home/paulf/build/src/amd64.amd64/lib/libc/libc.so.7.full /home/paulf/scratch/v

[Bug 259294] [libc] add a freeres function

2021-10-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 --- Comment #1 from Paul Floyd --- I'll see if I can work out a patch. In the meantime, here is the canonical C example #include int main(void) { printf("Hellw, World!\n"); } If I run valgrind --default-suppressions=no --leak-chec

[Bug 259294] [libc] add a freeres function

2021-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259294 Bug ID: 259294 Summary: [libc] add a freeres function Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects