https://sourceware.org/bugzilla/show_bug.cgi?id=32629
--- Comment #3 from Mark Wielaard <mark at klomp dot org> --- Aha, I see what you mean. I assumed this was just for DEBUGINFOD_URLS. But there are some others that don't have setter functions atm. DEBUGINFOD_CACHE_PATH, DEBUGINFOD_TIMEOUT, DEBUGINFOD_PROGRESS, DEBUGINFOD_VERBOSE, DEBUGINFOD_RETRY_LIMIT, DEBUGINFOD_MAXSIZE, DEBUGINFOD_MAXTIME and DEBUGINFOD_IMA_CERT_PATH. I am not sure any of them, except maybe DEBUGINFOD_VERBOSE, should be "reset" during the life time of the object. If you don't like the debuginfod_client handle you created, you just destroy it and create a new one with different settings. Changing them during usage feels confusing. It makes sense imho, specifically for DEBUGINFOD_URLS, DEBUGINFOD_CACHE_PATH and DEBUGINFOD_IMA_CERT_PATH to be fixed. It allows the implementation to keep the connection to the server, the cache dir and the cert files open for easy/fast reuse. -- You are receiving this mail because: You are on the CC list for the bug.
