Re: Recently-introduced segfault in initdb?

On 18 March 2018 at 05:57, Alvaro Herrera wrote: > Isaac Morland wrote: > > OK, I must have done something wrong with the bisect the first time. Now > > I'm getting the following as the problem commit: > > > > fd1a421fe66173fb9b85d3fe150afde8e812cbe4 is the first bad

Re: Recently-introduced segfault in initdb?

Isaac Morland wrote: > OK, I must have done something wrong with the bisect the first time. Now > I'm getting the following as the problem commit: > > fd1a421fe66173fb9b85d3fe150afde8e812cbe4 is the first bad commit Did you run "make distclean" before git-pulling? If not, maybe what you have is

Re: Recently-introduced segfault in initdb?

OK, I must have done something wrong with the bisect the first time. Now I'm getting the following as the problem commit: fd1a421fe66173fb9b85d3fe150afde8e812cbe4 is the first bad commit commit fd1a421fe66173fb9b85d3fe150afde8e812cbe4 Author: Peter Eisentraut Date: Fri Mar

Recently-introduced segfault in initdb?

I am trying to develop a small proof-of-concept patch for a proposal I have, but recently I found that initdb started segfaulting after I did a git pull. I used git bisect and it identified the following commit as the first one with the problem: 1733460f0205fc6d6bbe4c14911049a918c6e073 is the