Re: Help Resolving Compiler Errors With enable-dtrace Flag

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
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:47:38
Message-ID: 1da200de-588c-4d98-9d37-3e18640babee@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/20/24 12:02, Barry Walker wrote:
> Unfortunately the people remaining are just as lost as me. No one has
> attempted to build with dtrace so I'm in uncharted territory.

Was the customization done under version control?

If so then as last resort use bisect or equivalent to find the breaking
change?

>
> 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.

My mistake, was not paying attention. I meant to point the diff at:

~/src/backend/access/transam/xact.c

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Koen De Groote 2024-10-20 21:03:51 Re: Basebackup fails without useful error message
Previous Message Tom Lane 2024-10-20 19:32:32 Re: Help Resolving Compiler Errors With enable-dtrace Flag