public inbox for [email protected]  

help / color / mirror / Atom feed

From: Barry Walker <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: [email protected]
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
Date: Sun, 20 Oct 2024 15:02:06 -0400
Message-ID: <CAAiHg9UYgC93EHfLoNrWmWg3myvv5pdE91+USJ=1VvbyruJuqw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
	<[email protected]>

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 PM Adrian Klaver <[email protected]>
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
> [email protected]
>
>

view thread (5+ messages)  latest in thread

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: <CAAiHg9UYgC93EHfLoNrWmWg3myvv5pdE91+USJ=1VvbyruJuqw@mail.gmail.com>

* 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