[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2017-11-17 Thread andreas.longva_fraunhofer at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 --- Comment #1 from Andreas Longva --- Created attachment 42631 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42631&action=edit Attachments as described in the bug report

[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2017-11-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2019-04-20 Thread ppluzhnikov at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 Paul Pluzhnikov changed: What|Removed |Added CC||ppluzhnikov at google dot com --- Comm

[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2019-04-20 Thread ppluzhnikov at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 --- Comment #3 from Paul Pluzhnikov --- Reconfirmed with today trunk (r270470).

[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2019-04-21 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 --- Comment #4 from Jonathan Wakely --- Which version of glibc are you using?

[Bug libstdc++/83029] Memory leaks due to leaked thread local variable

2019-04-21 Thread ppluzhnikov at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83029 --- Comment #5 from Paul Pluzhnikov --- (In reply to Jonathan Wakely from comment #4) > Which version of glibc are you using? "Debian GLIBC 2.24-12". I believe this bug should be closed as fixed or invalid: 1. The original test case does not f