From: Tom Lane <tgl@sss.pgh.pa.us>
To: Barry Walker <mstrchef7@gmail.com>
cc: pgsql-general@postgresql.org
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
In-reply-to: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
References: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
Comments: In-reply-to Barry Walker <mstrchef7@gmail.com>
	message dated "Sun, 20 Oct 2024 12:30:55 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1371060.1729452752.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 20 Oct 2024 15:32:32 -0400
Message-ID: <1371061.1729452752@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1371061.1729452752%40sss.pgh.pa.us>
Precedence: bulk

Barry Walker <mstrchef7@gmail.com> writes:
> 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 s=
ome
> difference in the custom version that is causing the errors but I'm havi=
ng
> 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 f=
ind
> 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 an=
y
> differences in the custom version that is messing with the linker.

I'd read

https://www.postgresql.org/docs/current/dynamic-trace.html#DEFINING-TRACE-=
POINTS

and then go see if those tracepoints are fully conforming to the
coding rules in the modified version.  A plausible bet is that
their entries in probes.d don't entirely match up with the calls
in the source code.  You could compare the relevant bits of code
between vanilla and modified 16.4 if the problem isn't immediately
obvious.

			regards, tom lane