| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | glynastill(at)yahoo(dot)co(dot)uk |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Initdb problem on debian mips cobalt: Bus error |
| Date: | 2008-07-22 17:08:21 |
| Message-ID: | 420.1216746501@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Glyn Astill <glynastill(at)yahoo(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Wordsworth | 2008-07-22 17:40:23 | Re: pg_query transaction: auto rollback? begin or start?? commit or end??? |
| Previous Message | Bill Wordsworth | 2008-07-22 17:02:48 | pg_query transaction: auto rollback? begin or start?? commit or end??? |