Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsFkD-00H3yv-FL for pgsql-committers@arkaria.postgresql.org; Wed, 12 Mar 2025 06:39:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tsFkB-00FPcV-HO for pgsql-committers@arkaria.postgresql.org; Wed, 12 Mar 2025 06:39:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsFkB-00FPcN-3L for pgsql-committers@lists.postgresql.org; Wed, 12 Mar 2025 06:39:07 +0000 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsFk7-002MjQ-33 for pgsql-committers@lists.postgresql.org; Wed, 12 Mar 2025 06:39:04 +0000 Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-5497590ffbbso7058224e87.1 for ; Tue, 11 Mar 2025 23:39:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741761542; x=1742366342; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=+xsjXdnqQEnyRPfZQR1I4ZJ+9pnu+vJlhJjIpCL340w=; b=BcvXf7P9MYMrlv2QMOphWqH439A41X/BRVVJEtF4WPODOZ3B+YUdF1+brjZdToakp7 4mDiNvkJZVr+KErSglElyrvJQUI2YMN5BwNFI1bdWkWw9aCakUnhk5nnftKIq48G5izZ p3aRlrXOf2xI3r7IIEklyMtfR+AKZgEThbiLIocz+qNe4HQf3RyOfoGQqavVxNzmE0C5 ATnIBP1MuBGtW05gRTcWizpv8AsCrj+lj0baCVRHuIKh4efixSs59RfvRuTxomab86FN 4Nr8K1Kog/0jvonTUDBoVnTNIEMEE2iszf+mGBmhkrLxAS/KjvVYKiQ7ifg8OJaiDkb6 3wbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741761542; x=1742366342; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+xsjXdnqQEnyRPfZQR1I4ZJ+9pnu+vJlhJjIpCL340w=; b=P7CB34ohAe4Rq+6IChGjpbWQGRzjhQby+lMxsDoZV61UXEhnCcu2XaOAA1URDHPMV0 NM3xIvfBRBfxVXEf3kokoBOWpeT2kfK6xKL5DUF8mNsz50sx6qXlWyXAgi8l/H/tP6iH 3TDrzoBL4V1g3PH2LRilPqSjpyAKQTmf3mOhsf8Tb3PRrVKlRvw40p+M7gx1P/wK5+9Y tnx8oOFiwlRuFFkgPBo4pOOcKUH7Jt3E/74ifGgdJV5nQylZ35nWXBAaC6P+zqlC4l9t uIkFh4ZJxZFqvY70nFEqtNES9wMqEIWos9ZuGFAzclystC2AJcx9ySCnTVljmrh0sHkG HKLg== X-Forwarded-Encrypted: i=1; AJvYcCWusHWTmvGklNbU+m1NopXHsk4zoQJfwz5Zxx9bwgjNOruhP0FGWaSKe2N9PxJ8UIp2RNhtM44ve3ys2Jj4dhTo@lists.postgresql.org X-Gm-Message-State: AOJu0Yz1S0OfQE/buzY1sBCfYz66Myu+SjPSzQAouPSbi7YIPJiWJxYN gMKqbq26VAUPruLPOJSpkOtOtSPGFJMM7rR2Bw2vuo4gkYj8xycVJrUiWq2adDfS+jFZnGkn7Sd PxX5t1rWnqCuligecrYlehBVPW7s= X-Gm-Gg: ASbGncvRYP5cHr6GAhe78x1ABj/3q80RM/LinKY+m/SsTIhhxBDzZHobjmWwIvIcDj+ o3/yWudRMmeegLKNok0AHIEdVXR/2x6WOUadiwLludcJXAT8BCRJubTGfte2/tps1wdA8C04uHR yJZUSlg2hlY1Fq2g3foySeEnfnSgBnu29q5syHnD3PCKB1PrvruLnqD6x7IDQd X-Google-Smtp-Source: AGHT+IEELYOjjTDL0if7tEchRWF1nKCfUcQKo1VWumFqxSQytFSRILz9MNP+BbXM9IWiv5ALIjjeIq925S+wOZUoimg= X-Received: by 2002:a05:6512:3d8f:b0:545:c7d:1790 with SMTP id 2adb3069b0e04-54990e5da79mr7164094e87.22.1741761542317; Tue, 11 Mar 2025 23:39:02 -0700 (PDT) MIME-Version: 1.0 References: <1896564.1741756689@sss.pgh.pa.us> In-Reply-To: <1896564.1741756689@sss.pgh.pa.us> From: David Rowley Date: Wed, 12 Mar 2025 19:38:50 +1300 X-Gm-Features: AQ5f1JpFuL7tGNVbfRMnYftiZQRpWFNThPS2QHr4GU9iSy9-CFWmrkVM1Z7HYY4 Message-ID: Subject: Re: pgsql: pg_logicalinspect: Fix possible crash when passing a directory p To: Tom Lane Cc: Masahiko Sawada , pgsql-committers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 12 Mar 2025 at 18:18, Tom Lane wrote: > I don't know of an easy way. I experimented with doing this: > > diff --git a/src/include/c.h b/src/include/c.h > index a14c6315162..467b1f58ae8 100644 > --- a/src/include/c.h > +++ b/src/include/c.h > @@ -315,7 +315,7 @@ > #elif defined(_MSC_VER) && !defined(USE_ASSERT_CHECKING) > #define pg_unreachable() __assume(0) > #else > -#define pg_unreachable() abort() > +#define pg_unreachable() ((void) 0) > #endif > > /* > > which seems like it ought to be enough to provoke such warnings > (in assert-enabled builds). I got upwards of sixty build warnings > this way, but the place David mentions was *not* among them. > So I'm confused. Doing that for me does show the new warning. drowley@amd7945hx:~/pg_src$ meson setup -Dcassert=3Dtrue build > /dev/null && cd build && ninja | grep pg_logicalinspect.c [1962/2356] Compiling C object contrib/pg_logicalinspect/pg_logicalinspect.so.p/pg_logicalinspect.c.o ../contrib/pg_logicalinspect/pg_logicalinspect.c: In function =E2=80=98parse_snapshot_filename=E2=80=99: ../contrib/pg_logicalinspect/pg_logicalinspect.c:88:1: warning: control reaches end of non-void function [-Wreturn-type] drowley@amd7945hx:~/pg_src$ gcc --version gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0 David