* David Malcolm: > * gcc 16 -fanalyzer considers that any function that isn't explicitly > marked as "nothrow" could throw, and considers that as a possible > execution path through the code (here it would unwind the frame, and > thus leak the malloc). Maybe there could be better heuristics here; > could BIO_read or something it calls throw an exception?
BIO_read can throw because the BIO mechanism has callbacks for the underlying read implementaton. The question is whether OpenSSL supports throwing from the callbacks because it requires C libraries to be written in specific ways. There are other libraries that support this, whether it's for throwing exceptions or explicitly allowing longjmp from callbacks. Thanks, Florian -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
