From nobody Tue Nov 30 13:00:37 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2FD8318B7D55 for ; Tue, 30 Nov 2021 13:00:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J3MlX72Kjz3N32; Tue, 30 Nov 2021 13:00:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 77FD95595; Tue, 30 Nov 2021 13:00:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Message-ID: Date: Tue, 30 Nov 2021 15:00:37 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.3.0 Subject: Re: ctfconvert: rc = 1 Unsupported version [_dwarf_info_load(229)] Content-Language: en-US From: Andriy Gapon To: Mark Johnston Cc: FreeBSD Current References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1638277241; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lkYrXWax8znU1B5Zd/S8xDeSi7tjQxzxck2BMngrfzM=; b=LSl9RFl9LySSZBor1C8E30yxtR9br5QB4qVbqHm2RfwyiQlBAR8Du6O6DP2i7vhrCtIjSO jY6KLPZBnSpCckShoaj8swHmnt06Gphoo4dKnS+z/NOmPMfe2kMGFebX+cVfvA4JUGXKz8 TYfkdQTvUCkkEJbxXSjLTAka3lwxpWimn2B4PJi9HMqoZVJTQr7DZqnpolF7MZ20letYeS dRaaiEE4UDUaRFWcbWMfiNaAzprGADXJL0zkyKDXvf3JKa1eriC4TvgjrnxCza4iDB3k33 /r1H42v+CygLFKlAwlJIxi1yipLNYh5wFuctz47jaGCkLvjbmTTl/9Q67wkjeQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1638277241; a=rsa-sha256; cv=none; b=OUR/0YZ20DgtoO4ych57pBAf+pUh/9/h9y2oaWaZcwhvQLpjYvxxBGjKNcxy04N0FT7nCv CJAoz8kuIi0cm6jr+6+5JxzL776utpvcDgLow2aV0E+EAueGnLgqoi15pGWyCBxUcCGd0k dNG7Rf5gyMV0J57nH/7CfWC5U8BM6NOIEwo7PoxlINjBk/zsS3+ylwLdqymsaJl37vqbjA awBFy3jNLUEGG4OHJsgWobdGytL3Tzff23YI/HjvMMUQyRm7tnpSeShGFUdqmAtDF2U6rv 9iPS8KGobkkVfnYfx8ZMh0tyigrKkDKyYdiI+7IPfZR6edHnO/wFro8E0nDvSg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 27/11/2021 10:42, Andriy Gapon wrote: > On 26/11/2021 21:48, Mark Johnston wrote: >> On Fri, Nov 26, 2021 at 02:00:27PM -0500, Mark Johnston wrote: >>> Thanks, I can reproduce it now. >>> >>> Our libdwarf is complaining that the first compilation unit header in >>> .debug_info contains an unsupported DWARF version number (libdwarf only >>> supports 2, 3 and 4).  In files compiled by clang it ends up being zero. >>> For instance, compiling bin/cat and dumping the .debug_info section: >>> >>> gcc10: >>>   c1250000 04000000 00000801 00000000 >>>             ^ DWARF version >>> clang: >>>    01000000 00000000 4e230000 00000000 >>> >>> llvm-dwarfdump and binutils readelf are somehow still able to find a >>> valid-looking unit header, but I haven't yet been able to figure out how >>> they do that from reading the DWARF 4/5 specs or the LLVM sources. >> |Ah, we recently started configuring clang to compress debug sections by >> default, and our libdwarf doesn't know how to handle that. As an interim >> workaround this could simply be disabled with WITH_CTF is configured: > > Oh wow, you were very fast at figuring this out. > Thank you very much! > > I'll give the build change a whirl first and then test D33139 a bit later. Tested both (individually) and both do the job just as expected. -- Andriy Gapon