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 1t2bC3-005N3z-Em for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 19:02:23 +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 1t2bC1-000elz-1x for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 19:02:21 +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 1t2bC0-000elr-IV for pgsql-general@lists.postgresql.org; Sun, 20 Oct 2024 19:02:20 +0000 Received: from mail-vs1-xe31.google.com ([2607:f8b0:4864:20::e31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t2bBy-001sks-D1 for pgsql-general@postgresql.org; Sun, 20 Oct 2024 19:02:19 +0000 Received: by mail-vs1-xe31.google.com with SMTP id ada2fe7eead31-4a4861a689eso873667137.2 for ; Sun, 20 Oct 2024 12:02:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729450937; x=1730055737; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uWQccJfqP30KDyd9hIwUP4jdk5h045mk+k9/C9kzlJs=; b=hyclmJpPFikVQd3H/7AKyZ7KUdKD4EK+XaUN+pHfNiPqkGcbSOBTsrG+XkU8/pLU3B lqiV0TEAXtX9Nm0/nDkuDFI7gHVbYO18EMP4oUXRh0Eg07G9ZPnUp8IZEeLvRZSpVMBq JrfVBcF+s5NlZ02UquMbYOgMgap6u2dD8k4YNMZogN12ZZ3bV+6pCuL5wOFOSqjitFCH aFzSwlbP+9Rxm1W6uOJFVWT0dGXuM4qXEEDeT96Z1m4lU9Szt5YclJG+yY8S6n7GFTwM /V7GfsTvNHMBtZf+wbub3dbHwYRuQG7j5kb0D7UtmcAmRPJwmONtHsVLJP2iv2n7X8dE 31pA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729450937; x=1730055737; h=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=uWQccJfqP30KDyd9hIwUP4jdk5h045mk+k9/C9kzlJs=; b=N1ujtU4mdWIOiBNR6hYUL929sCXDoFoxIBTL7NZhHxiQdQB4URnWK08gVI5JtSGrAk aarwy0vNUht1WKJH8Kt+OYMaTTJO5r09cRc2k9AjlreRR+f725RIsky/3g+nRNP3kWhY w5OecburhAKIlEfWodpj3fM+cs11MV/hUSpJ9W8Gbg0++3bSp6ZjhHDCKFpd8Kieps2Q U0sZ19nb4o81v9WtzjV1ov/Xexv9k1uHDX2Je2/XiYQg2KmHdLwO6luzZebn2cfRlgda p3PXJSKjiP9bY1OD5K/KK/NVqMC1Bc2VfciPm7W3PkpR3jCx8JMWHnKAsOioDTKPDO0e Hyqw== X-Gm-Message-State: AOJu0YwuFKJegtom5cBmIu5nKyIs7qnqN2bpe1sw3xUp0hsWd1SWTlv8 XJjT0PBNqoVdR8mnKRVTrNXZE+VOPgaMgGaa5nXdVdwDflCpNemzMTAohVqjfA7qltu1xmOljZb mE9Bi5eKp2LXWgOTLodBUvo4QBo8dfhMSPt4= X-Google-Smtp-Source: AGHT+IFPSUm7NiBizoVaz9jWs9bDaUHpv8N5LSt14HIalYgCL5FfQLI2Z4LnyIFnek0L7Bhw2IS1+Fqvt1JCA9smckM= X-Received: by 2002:a05:6102:a4e:b0:4a4:9253:9ba3 with SMTP id ada2fe7eead31-4a5d6ac9066mr7422198137.15.1729450937482; Sun, 20 Oct 2024 12:02:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Barry Walker Date: Sun, 20 Oct 2024 15:02:06 -0400 Message-ID: Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag To: Adrian Klaver Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000c909350624ed2c07" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c909350624ed2c07 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Unfortunately the people remaining are just as lost as me. No one has attempted to build with dtrace so I'm in uncharted territory. A diff of the object file doesn't give any useful information, the custom version has a lot of differences since there have been a number of changes from stock. postgresql_transaction__commit_semaphore does exist in the symbol table of both .o files though when compared with objdump. On Sun, Oct 20, 2024 at 1:50=E2=80=AFPM Adrian Klaver wrote: > On 10/20/24 09:30, Barry Walker wrote: > > Hey folks, > > > I have compiled vanilla pg16.4 with the same flags and the probes got > > created and linked as expected with no issues so I'm assuming there is > > some difference in the custom version that is causing the errors but I'= m > > having a hard time tracking it down. I'm wondering if anyone here has > > any experience with this error or has any hints as to why the linker > > can't find these definitions or even just where the actual definitions > > for these probes should live so I can try to work backwards and see if > > there is any differences in the custom version that is messing with > > the linker. > > Talking to the folks that created the custom version is not possible? > > If you do a diff on: > > access/transam/xact.o > > between the stock and custom version does it shed any light? > > > > > Thanks! > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --000000000000c909350624ed2c07 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Unfortunately the people remaining are just as lost a= s me. No one has attempted to build with dtrace so I'm in uncharted ter= ritory.

A diff of the object file doesn't give= any useful information, the custom version has a lot of differences since = there have been a number of changes from stock.=C2=A0postgresql_transaction= __commit_semaphore does exist in the symbol table of both .o files though w= hen compared with objdump.

On Sun, Oct 20, 2024 at 1:50=E2=80=AFPM Adrian Kl= aver <adrian.klaver@aklaver= .com> wrote:
On 10/20/24 09:30, Barry Walker wrote:
> Hey folks,

> I have compiled vanilla pg16.4 with the same flags and the probes got =
> created and linked as expected with no issues so I'm assuming ther= e is
> some difference in the custom version that is causing=C2=A0the errors = but I'm
> having a hard time tracking it down. I'm wondering if anyone here = has
> any experience=C2=A0with this error or has any hints as to why the lin= ker
> can't find these definitions or even just where the actual definit= ions
> for these probes should live so I can try to work backwards and see if=
> there is any differences in the custom version that is messing with > the=C2=A0linker.

Talking to the folks that created the custom version is not possible?

If you do a diff on:

access/transam/xact.o

between the stock and custom version does it shed any light?

>
> Thanks!

--
Adrian Klaver
adrian.klave= r@aklaver.com

--000000000000c909350624ed2c07--