From nobody Fri May 06 12:25:54 2022 X-Original-To: freebsd-hackers@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 90D091ABE1BB for ; Fri, 6 May 2022 12:25:58 +0000 (UTC) (envelope-from benjamin.bannier@corelight.com) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 4KvqY13vmyz51L7 for ; Fri, 6 May 2022 12:25:57 +0000 (UTC) (envelope-from benjamin.bannier@corelight.com) Received: by mail-ej1-x62d.google.com with SMTP id i19so14134927eja.11 for ; Fri, 06 May 2022 05:25:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=corelight.com; s=corelight.com; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=/lwp5tx7HHnIGTgtxR/eTi2IJaQEA16y6B7aqfTD6zs=; b=cPViQJOi6Y79hF1Hq+uWZ3ABMG+njKreB9MZOvM28D72EYJWQf33lKwT9R5fI/dSCs bfwgRzIGvxWPBVUbY3DRzBYWV3UN0YIASa/2IQKi0VinQ8tcy9kIdPi3SguvOYOJpU5Q elGFsaTd7Dr0fLnDZAHDyVwBGaJsdBp/N58dmC9T/SI9lPeT7Ere8IgAYoam8WMTpnWq Ouvap5Ngq3u5HKD6a5aNvBAC/FVPr2gQ/ILWgowLGwvCyaCnVeYa3AArrHQynyjfqlwh LPxcGfOdJtQuIDUrt04G3MoFATpzQ1r9YYWlILssncXfcsWaNrgns1aagiGqlvqtkOwH 1DEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=/lwp5tx7HHnIGTgtxR/eTi2IJaQEA16y6B7aqfTD6zs=; b=5XC9nvUKtmebCYjtoAXpaZjJL//3a3P7kTPRNJpl9GMTT060gTyvwU0vqMeE3OcnOY 2lrIFEXLfLDNR1doHE/wolz8t2xMK9bBdCL+yfiDXDWUn3McSVLl+eYquntN4FwL74/+ yX6eXXP+tlFHmFMa2AoJE2Q7GB2Jf9UBCf9EGxKqvuASq3eokdVoQIDh5qcMy/PzxQIb YyTK+A0jB0ZoJ33/VpiANbmdW+p9xWWaYPBHb9S+PzWrZUKiBrNxYoCoA1eA9RvybeIg 7BrcUhvJu/7zrSbm3Uz8Zsjx/M+9WMZ46bk+YA7Yiyj5xi9uIWavRLNh8NqRAClYcPlV AlAQ== X-Gm-Message-State: AOAM530mO7lct7rSS914UUM3Qlk0J+CgizfewKgxhQnZoIxKV08RcwHd U8jY09eYzqkZo/72lWADMWq2XpxtcS/AA14sZFHEn/yluRIfoxjcRM712mYvdwnqdUXrrbhfmX8 +ITeA4Ia1V8FyZ36OfAdt5bRPkuCC0ZMQbJAU2vuZXNqvrEsPYIw1qRohmQhL0qPpknmGlpVMQQ XbA5U3QtPYdrFjEjPcAA== X-Google-Smtp-Source: ABdhPJx0FjtrKPX4BRTJTleLQEI30AuAOwJL02wV6fObHnsp4JmDGRgiZ81z+jCJx0f5yG3GHeHP+w== X-Received: by 2002:a17:907:6d24:b0:6f4:bc43:e7d1 with SMTP id sa36-20020a1709076d2400b006f4bc43e7d1mr2638743ejc.581.1651839956223; Fri, 06 May 2022 05:25:56 -0700 (PDT) Received: from flux.fritz.box (dslb-090-186-125-058.090.186.pools.vodafone-ip.de. [90.186.125.58]) by smtp.gmail.com with ESMTPSA id dq8-20020a170907734800b006f3ef214deasm1890209ejc.80.2022.05.06.05.25.55 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 May 2022 05:25:55 -0700 (PDT) From: Benjamin Bannier Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: abi::__cxx_demangle appears to be broken on vanilla freebsd-13.0 Message-Id: Date: Fri, 6 May 2022 14:25:54 +0200 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3608.120.23.2.7) X-Rspamd-Queue-Id: 4KvqY13vmyz51L7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=corelight.com header.s=corelight.com header.b=cPViQJOi; dmarc=none; spf=pass (mx1.freebsd.org: domain of benjamin.bannier@corelight.com designates 2a00:1450:4864:20::62d as permitted sender) smtp.mailfrom=benjamin.bannier@corelight.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[corelight.com:s=corelight.com]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[corelight.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[corelight.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62d:from]; MLMMJ_DEST(0.00)[freebsd-hackers]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[90.186.125.58:received] X-ThisMailContainsUnwantedMimeParts: N Hi, I am trying to add support for a C++ program which makes use of = `abi::__cxx_demangle` for name unmangling. This worked well up to = freebsd-12.2, but appears to be broken on a vanilla 13.0. Example: // foo.cc #include #include #include int main() { const std::type_info &info =3D typeid(std::type_info); const char *name =3D info.name(); int status =3D 0; const char *dname =3D abi::__cxa_demangle(name, NULL, NULL, = &status); if (status !=3D 0) { std::cerr << "status=3D" << status << ' ' << name << '\n'; return 0; } std::cerr << name << ' ' << dname << '\n'; } This can be built with e.g., `make`: make foo If I run this on a vanilla freebsd-12.2 `__cxa_demangle` can demangle = the name as mangled by the system: $ ./foo St9type_info std::type_info On vanilla freebsd-13.0 OTOH `__cxa_demangle` reports `status=3D-2` = which according to = https://panthema.net/2008/0901-stacktrace-demangled/cxa_demangle.html = means: > -2: mangled_name is not a valid name under the C++ ABI mangling rules. I found a number of issues in bugzilla on broken unmangling in `c++filt` = and mentions of workaround which went in to fix that, but on a vanilla = 13.0 even `c++filt` seems unable to demangle `name`. I also found = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222563 which seems = to have staled for a long time (left a ping there). Could somebody point me to a way to fix this behavior? I cannot image = that I am the only one having this issue. Cheers, Benjamin=