Re: Help Resolving Compiler Errors With enable-dtrace Flag

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Barry Walker <mstrchef7(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
Date: 2024-10-20 19:32:32
Message-ID: 1371061.1729452752@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Barry Walker <mstrchef7(at)gmail(dot)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 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2024-10-20 19:47:38 Re: Help Resolving Compiler Errors With enable-dtrace Flag
Previous Message Tom Lane 2024-10-20 19:19:00 Re: Using Expanded Objects other than Arrays from plpgsql