From nobody Fri Nov 26 19:00:27 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 E8C4118B1AE4 for ; Fri, 26 Nov 2021 19:00:31 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J13wb64hKz4WFx; Fri, 26 Nov 2021 19:00:31 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd2d.google.com with SMTP id b187so1415355iof.11; Fri, 26 Nov 2021 11:00:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=uLbOjhUxGn3jU7ZzT0JWc+8f8VArUGUEaaDgAFzVJ/k=; b=SxvJLHZ+ovQbYzgYcyfrco9AabISLBIXU3J4OXSAJh5e6gkRVShnyi9ruI9mufmAo4 hWKIRGcL0ccvGD215QuMvfG/eUd4XNjAAl5vk8GtGUWHDeK9nDMQXN9/JucggXwzDrjS nss4O9EfeTe+L4KTiGexX/yD8y+JQhB5FPH5Lp3TlUEgahP+ZkP061qZxFlrdxq2y03D q/+wTD4JcJK+zAXinmqzr0VBQAgeaXfpEV+l9EQRwziO8vqW2xTKU4rYycJrDwsFGjl+ neYBX0FxS/xjHLL79O3RcluLf0ArXN6+LgbXPNv/+9IHyqDZ9vmSokMqCHbJSm6hK7zk 3bsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=uLbOjhUxGn3jU7ZzT0JWc+8f8VArUGUEaaDgAFzVJ/k=; b=IFJAJBcdiwxxQJ/C2aYN3Z86bIrUgXTFRkTE9C4ypyVbVuYKTsPBCBcVyipN55MT64 NGFvNuv7IhO7/k2WJBsrVT2TE8TTx9qQrS6CPMSIXzKT56yRmLCO3J5ULFSqePqnCaUE zOahvRcONWVIrP8LX8ygY5yFvBP7o37RmGyVoJ3BAIdkxeg/mIDpGTu0YAEIsIuX8SqC MQ8GYOLPDFo+Ya8KGyNPtPYxiQYxUdAiYpmLM4OrVEgTMbo/YSMxEDG7EnAJQaDy3Zan jIg16zScEdwd3nQpPUnAqd8L6qaS2XMOh4BHKXd9yfJeRZUNiivx33PyqwVcC5AATkjC GpQw== X-Gm-Message-State: AOAM5317VGNaE2o48m/U+L2m+n4i84I6MZx5yoygf7m0hXbnFsKuvuFn qjUkczNO4TCqFiSm+0idM8gSgBpcHa4= X-Google-Smtp-Source: ABdhPJz9YIHotZv7O4rF8okRdj/L5t2MxWZyCON+2p3XLmBdHKcow093epR1VyuC7rMFfnTA1GlTjA== X-Received: by 2002:a05:6638:2054:: with SMTP id t20mr47298792jaj.42.1637953230353; Fri, 26 Nov 2021 11:00:30 -0800 (PST) Received: from nuc ([142.126.186.191]) by smtp.gmail.com with ESMTPSA id o10sm3506571ioa.26.2021.11.26.11.00.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Nov 2021 11:00:29 -0800 (PST) Date: Fri, 26 Nov 2021 14:00:27 -0500 From: Mark Johnston To: Andriy Gapon Cc: FreeBSD Current Subject: Re: ctfconvert: rc = 1 Unsupported version [_dwarf_info_load(229)] Message-ID: References: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4J13wb64hKz4WFx X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, Nov 26, 2021 at 06:12:49PM +0200, Andriy Gapon wrote: > On 26/11/2021 18:06, Mark Johnston wrote: > > On Thu, Nov 25, 2021 at 10:48:36PM +0200, Andriy Gapon wrote: > >> > >> I've just finished builds of yesterday's CURRENT / main for arm and arm64. > >> In both builds I got lots of messages from ctfconvert: > >> ctfconvert: rc = 1 Unsupported version [_dwarf_info_load(229)] > >> > >> I got an impression that there was a message for each object file, that's how > >> many of them were there. > >> > >> I don't recall seeing those messages before. > >> > >> Should I be concerned? > >> Maybe I am doing something wrong or have an unusual configuration? > >> Any way to fix the issue? > >> > >> Thanks! > >> > >> P.S. > >> The builds were done on stable/13, so maybe there is an issue with host tools > >> not being able to grok something new. > > > > I haven't seen this before, for what it's worth. I presume this is from > > a kernel build? Does the configuration enable generation of debug info > > with, e.g., "makeoptions DEBUG=-g"? > > This is actually from buildworld. > buildkernel is silent. 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.