Re: Question about debugging bootstrapping and catalog entries - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: Question about debugging bootstrapping and catalog entries
Date
Msg-id E1539E0ED7043848906A8FF995BDA5790198F32F@m0143.s-mxs.net
Whole thread Raw
In response to Re: Question about debugging bootstrapping and catalog entries  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Question about debugging bootstrapping and catalog entries
List pgsql-hackers
> > Are there any tricks people have for debugging bootstrapping
processing? I
> > just need to know what index it's trying to build here and that
should be
> > enough to point me in the right direction:
>
> Here's what I did: you can step over functions in initdb until it
fails
> (although I alredy know which part it's failing I guess). Restart.
Then
> you go into that function and step until the new backend has been
> started. At this point you attach another gdb to the backend and let
it
> run.

How do you attach fast enough, so not all is over before you are able to
attach ?
I'd like to debug initdb failure on Windows (postgres executable not
found) when
running make check with disabled is_admin check and --prefix=/postgres
in msys.

The program "postgres" is needed by initdb but was not found in the
same directory as
"j:/postgres/src/test/regress/./tmp_check/install/postgres/bin/initdb".

Andreas


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Question about debugging bootstrapping and catalog entries
Next
From: Gregory Stark
Date:
Subject: Re: Question about debugging bootstrapping and catalog entries