On 1/6/26 2:41 PM, Ales Musil via dev wrote: > The memory leak reported by GCC with sanitizers (below) is a false > positive in a way, the process is ending before the free of the > options is called so it doesn't cause any harm. It is freed properly > in a flow where the process keeps running. The opt to skip rather > than call the free is that certain options lead to direct exit > without proper free and fixing all of them would probably cause > more harm, on the code readability front, than good. > > Direct leak of 49 byte(s) in 1 object(s) allocated from: > malloc (/workspace/ovn-tmp/northd/ovn-northd+0x787e1f) > xmalloc__ lib/util.c:141 > xmalloc lib/util.c:176 > xmemdup0 lib/util.c:197 > xstrdup lib/util.c:206 > ovs_cmdl_long_options_to_short_options lib/command-line.c:53 > parse_options northd/ovn-northd.c:660 > main northd/ovn-northd.c:870 > > Signed-off-by: Ales Musil <[email protected]> > ---
Hi Ales, Thanks for the fix! Applied to main. Regards, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
