| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CVS HEAD busted on Windows? |
| Date: | 2006-06-21 15:07:30 |
| Message-ID: | 10380.1150902450@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> Hmmm, running it more interactively I see what was probably the hang
> when run from the scheduler:
> ---------------------------
> psql.exe - Application Error
> ---------------------------
> The instruction at "0x7c8396d0" referenced memory at "0x00000014". The
> memory could not be "read".
Well, that's pretty clearly a null pointer dereference. Any chance of
mapping the instruction address back to something useful?
This being a psql-side crash, it couldn't be related to the symptom
we saw before of initdb not finding postgres.exe. I'm starting to
wonder if maybe that machine has suddenly developed an intermittent
memory fault or some such. Have you noticed any other flaky behavior?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-06-21 15:14:36 | Re: CVS HEAD busted on Windows? |
| Previous Message | Tom Lane | 2006-06-21 15:02:47 | Overhead for stats_command_string et al, take 2 |