Glyn Astill <glynastill@yahoo.co.uk> writes:
> And, the instruction pointer info:
> (gdb) x/i $pc
> 0x7572d0 <InitializeGUCOptions+648>:
> beqz v0,0x75748c <InitializeGUCOptions+1092>
Huh. The pc could possibly be a bit off from reality in this type of
error, but none of the instructions immediately around it look like they
could be making a bogus memory access either. The only thought that
comes to mind is that the branch is being attempted but there's garbage
at InitializeGUCOptions+1092 ? Try "x/32i InitializeGUCOptions+1092"
What ulimit settings are operative anyway? (ulimit -a might tell you)
regards, tom lane
