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 117383858D37 for ; Thu, 20 Apr 2023 10:07:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 117383858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681985234; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=bIHkjceQumMs7QdPxmFqTi0Zx79BwX2UhwZWXj8yIao=; b=OGzPM7FeRexd34hyQnweNhrW9WvqwSGbxkl9dNj7OlMW+9NPefHbd6RD5IyDCRGa6e68h4 +XhNTsoYmumke47OHcQye8dYOvlVP11gis5uyzeijZ0i4DE7BzM0bicxPCDAvXf8dVKlv9 hPCNBS8hX5HGEB1631XCoW5kR3kD9jw= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-617-xG94UawxPimvJW-IQ6IrZA-1; Thu, 20 Apr 2023 06:07:11 -0400 X-MC-Unique: xG94UawxPimvJW-IQ6IrZA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 258293806701; Thu, 20 Apr 2023 10:07:11 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A2AEC440BC; Thu, 20 Apr 2023 10:07:10 +0000 (UTC) From: Florian Weimer To: Matthew Chae via Libc-help Cc: Matthew Chae Subject: Re: The question about _dl_catch_exception References: Date: Thu, 20 Apr 2023 12:07:09 +0200 In-Reply-To: (Matthew Chae via Libc-help's message of "Thu, 20 Apr 2023 05:21:08 +0000") Message-ID: <875y9qg94i.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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 List-Id: * Matthew Chae via Libc-help: > I have to solve some issue which is generating signal 11(SIGSEGV, > segmentation fault) in the "_dl_catch_exception" in glibc v2.30. > > 1. I noticed that the below has been added since v2.31. > > I'm looking into whether this is helpful to solve my issue. > > Is it possible that the exception variable becomes NULL? Not really in glibc 2.30, I think. > 2. Can I get some ideas on which case segmentation fault can be generated in the "_dl_catch_exception"? There have been quite a few issues, particularly around dlmopen/audit, but they impact ld.so exception handling in general, not specifically _dl_catch_exception. It's hard to tell what could be the cause in your case without more details. Thanks, Florian