Bug#222130: [PATCH] : fix invalid __libc_dlclose() in nsswitch.c

Hi, So any comments or questions on this report? Any reason there hasn't yet been a response? To summarize: Handles are marked as -1 (not as NULL) if a lookup fails. The code should look for that -1 before trying to free the handle or it will call free() with an invalid pointer. Upstream cvs

Bug#222130: [PATCH] : fix invalid __libc_dlclose() in nsswitch.c

Hi, So any comments or questions on this report? Any reason there hasn't yet been a response? To summarize: Handles are marked as -1 (not as NULL) if a lookup fails. The code should look for that -1 before trying to free the handle or it will call free() with an invalid pointer. Upstream cvs

Bug#222130: [PATCH] : fix invalid __libc_dlclose() in nsswitch.c

tags 222130 patch quit Hi, I get similar behavior here on a variety of Debian systems (stable, testing and probably unstable too since I checked glibc cvs and the bug is there). I believe this is the same bug as the original submitter reported, at least the valgrind spew at exit is strikengly

Bug#222130: [PATCH] : fix invalid __libc_dlclose() in nsswitch.c

tags 222130 patch quit Hi, I get similar behavior here on a variety of Debian systems (stable, testing and probably unstable too since I checked glibc cvs and the bug is there). I believe this is the same bug as the original submitter reported, at least the valgrind spew at exit is strikengly