From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 3E4B93858D37 for ; Fri, 5 Aug 2022 08:38:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3E4B93858D37 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-81-7OhhaQSTPROhwXVqv8VcRg-1; Fri, 05 Aug 2022 04:38:42 -0400 X-MC-Unique: 7OhhaQSTPROhwXVqv8VcRg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7989385A585; Fri, 5 Aug 2022 08:38:42 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.51]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B74052026D4C; Fri, 5 Aug 2022 08:38:41 +0000 (UTC) From: Florian Weimer To: Po Lu Cc: Po Lu via Libc-alpha Subject: Re: Hook for `_exit' References: <87les389c6.fsf.ref@yahoo.com> <87les389c6.fsf@yahoo.com> <871qtv2j7w.fsf@oldenburg.str.redhat.com> <87o7wz6qb5.fsf@yahoo.com> Date: Fri, 05 Aug 2022 10:38:39 +0200 In-Reply-To: <87o7wz6qb5.fsf@yahoo.com> (Po Lu's message of "Fri, 05 Aug 2022 16:35:26 +0800") Message-ID: <87r11v13w0.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2022 08:38:50 -0000 * Po Lu: > Florian Weimer writes: > >> I think even if we add the hook in glibc, GTK will find a way to >> terminate the process immediately by other means. > > GTK 3 is already in maintenance mode, so I doubt their developers will > deliberately break programs relying on such a hook. In any case, it > will let us ship a fix for this common problem to our users now, and > negotiate with the GTK developers later should they break it. It sounds like a bad idea to adopt a library that is already in maintenance mode. Why do you expect that its successor will handle this differently? Does the successor use exit? Thanks, Florian