Re: Segfaults with 8.1.3 on amd64

From: "Guy Rouillier" <guyr(at)masergy(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Segfaults with 8.1.3 on amd64
Date: 2006-05-04 15:29:56
Message-ID: D4D1632DC736E74AB95FE78CD609007901262A@mtxexch01.add0.masergy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martijn van Oosterhout wrote:
> On Thu, May 04, 2006 at 12:22:01PM +0100, Gavin Hamill wrote:
>> Hi, our 8.1.3 system on quad Xeon has been happily chugging away for
>> weeks with no stability problems until yesterday:
>>
>> /var/log/syslog:May 4 11:57:17 cayenne kernel: postmaster[19291]:
>> segfault at 0000000000000000 rip 00002aaaab5e8c00 rsp
>> 00007fffffffd418 error 4
>
> <snip>
>
>> I don't know what the rip + rsp values represent, but is it
>> interesting that they are identical in all three cases?
>
> At a guess rip = return instruction pointer, rsp = return stack
> point. The fact that they're all the same seems to rule out hardware.

The R* registers in AMD64 are just the 64-bit extensions to the standard
registers. They couldn't use EIP because that was taken in the
expansion from 16-bit to 32-bit. So RIP is simply the 64-bit
instruction pointer, RSP the 64-bit stack pointer.

--
Guy Rouillier

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2006-05-04 16:17:31 Re: Adding ON UPDATE CASCADE to an existing foreign key
Previous Message Rich Doughty 2006-05-04 15:18:01 Adding ON UPDATE CASCADE to an existing foreign key constraint