[Bug analyzer/110172] Leak false positives from -fanalyzer with -fexceptions (even on C code)

2023-06-20 Thread fw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110172 Florian Weimer changed: What|Removed |Added CC||fw at gcc dot gnu.org --- Comment #5

[Bug analyzer/110172] Leak false positives from -fanalyzer with -fexceptions (even on C code)

2023-06-20 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110172 --- Comment #4 from Xi Ruoyao --- (In reply to Jonathan Wakely from comment #3) > I mentioned that on IRC. I'm not sure glibc can even handle exceptions from > those functions. Is that supported at all? Does printf clean up its own >

[Bug analyzer/110172] Leak false positives from -fanalyzer with -fexceptions (even on C code)

2023-06-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110172 --- Comment #3 from Jonathan Wakely --- I mentioned that on IRC. I'm not sure glibc can even handle exceptions from those functions. Is that supported at all? Does printf clean up its own allocations and locks in that case? IMHO it should be UB

[Bug analyzer/110172] Leak false positives from -fanalyzer with -fexceptions (even on C code)

2023-06-20 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110172 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #2

[Bug analyzer/110172] Leak false positives from -fanalyzer with -fexceptions (even on C code)

2023-06-20 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110172 --- Comment #1 from David Malcolm --- Quoting: https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#index-fexceptions """ -fexceptions Enable exception handling. Generates extra code needed to propagate exceptions. For some targets,