Re: CVS HEAD busted on Windows?

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:26:23
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E401388AD2@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 21 June 2006 16:08
> To: Dave Page
> Cc: Peter Eisentraut; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] CVS HEAD busted on Windows?
>
> "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?

Not sure how I would do that. Any hints?

> 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?

Nope. 8.0 and 8.1 build fine now they're run from separate scheduler
jobs. The management card hasn't reported any errors, and it's a server
grade box with ECC RAM, RAID 10 disks etc. Plus Andrew's seeing a
similar issue of course...

Regards, Dave.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-06-21 15:31:56 Re: CVS HEAD busted on Windows?
Previous Message Andrew Dunstan 2006-06-21 15:14:36 Re: CVS HEAD busted on Windows?