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.133.124]) by sourceware.org (Postfix) with ESMTPS id 18A1B3858D1E for ; Mon, 19 Dec 2022 13:04:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 18A1B3858D1E 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=1671455078; 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: references:references; bh=bxod0f8wGgtUjPJVfYKS3xTXhcu+Sy0hi5ZTkZ7kvJ4=; b=TlLpXjTbh/hY+Z2PaFairMjvFtVbtkAMmMCiGnPa7XFoupTdu4RRYBrwINVQPw3qPgGpHJ LjVhg3T7bx/4sLrXUzJZuU4mfxvFKwjiYT1FDw8PNcwDRnIRX2Ii/SJBhHAq77VsEbgBS4 qxDrg+QS/4nHnIQe6zEkvdGPhocrI9s= 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-462-eCB4QaS_P5SCpqvP7EvbdA-1; Mon, 19 Dec 2022 08:04:35 -0500 X-MC-Unique: eCB4QaS_P5SCpqvP7EvbdA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3671B87A381; Mon, 19 Dec 2022 13:04:35 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.56]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 17682C15BAD; Mon, 19 Dec 2022 13:04:35 +0000 (UTC) Received: from [127.0.0.1] (helo=vm-rhel7) by redhat.com with esmtp (Exim 4.94.2) (envelope-from ) id 1p7Fon-0005EP-GC; Mon, 19 Dec 2022 08:04:34 -0500 From: fche@redhat.com (Frank Ch. Eigler) To: Simon Marchi Cc: Alexandra =?utf-8?B?SMOhamtvdsOh?= , gdb-patches@sourceware.org Subject: Re: [PATCH] gdb: defer warnings when loading separate debug files Date: Mon, 19 Dec 2022 08:04:01 -0500 References: <20221212121535.4013497-1-ahajkova@redhat.com> Message-ID: <87cz8fr1cv.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-7.7 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 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: Simon Marchi via Gdb-patches writes: > [...] > I don't really like this behavior change. The situations you described: > > - a separate debug file without any actual debug information > - CRC checksum that doesn't match > > ... are abnormal situations which still deserve being warned about, I > think. If the files are there, it's because they are meant to be > used, That's a bit of a leap. They can happen totally accidentally, when a sysadmin or cron job does an automated update of the system, and for whatever reason, the debug packages got missed. On some distros, this can easily happen. Then the remnants are not "meant to be used" at all, they are just fossils. > so if something prevents GDB from using them, I want to know. > Silencing the warning just makes investigating "why doesn't GDB read > my separate debug file" harder. If GDB did find the correct debug file one way or the other, then why would you care, never mind bother investigate? It's a non-problem. > I can understand why this can be a bit confusing to the user, but > the warning is still factually correct. For instance, the one you > quoted: > > warning: the debug information found in > "/usr/lib/debug//lib64/ld-2.32.so.debug" does not match > "/lib64/ld-linux-x86-64.so.2" (CRC mismatch). Ideally, users should really only be warned about things that they can do something about. Being warned about the same thing that only a sysadmin can possibly fix, and repeatedly, seems more like noise. - FChE