On Mon, Nov 8, 2021 at 12:09 PM Noah Misch <noah@leadboat.com> wrote:
On Mon, Nov 08, 2021 at 11:22:45AM +0500, Semab Tariq wrote: > On Mon, Nov 8, 2021 at 4:22 AM Noah Misch <noah@leadboat.com> wrote: > > Thanks. That shows the crash happened sometime after strcmp(defval1->adbin, > > defval2->adbin). Please run the attached version, > > PFA the new log file
> 0x40000000003fdc30:2 in equalTupleDescs (tupdesc1=0x60000000001fdb98, tupdesc2=0x6000000000202da8) > 0x40000000003fdc30:2 <equalTupleDescs+0x10e2>: br.call.sptk.many rp=0x3fffffffff3fdc30 > 0x3fffffffff3fdc30 in <unknown_procedure> () > 0x3fffffffff3fdc30: Error accessing memory address 0x3fffffffff3fdc30: Bad address.
This postgres binary apparently contains an explicit branch to 0x3fffffffff3fdc30, which is not an address reasonably expected to contain code. (It's not a known heap, a known stack, or a CODE section from the binary file.) This probably confirms a toolchain bug.
Would you do "git checkout 166f943" in the source directory you've been testing, then rerun the test and post the compressed tmp_check/log directory?
So make command fails after I applied the v0.4 patch to 166f943 also it did not create any tmp_check/log directory
PFA make output
I'm guessing that will show the bad branch instruction no longer present.