public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Barry Walker <[email protected]>
Cc: [email protected]
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
Date: Sun, 20 Oct 2024 15:32:32 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
References: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>

Barry Walker <[email protected]> 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 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.

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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox