Re: We've broken something in error recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: We've broken something in error recovery
Date: 2010-01-23 21:35:52
Message-ID: 15246.1264282552@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> #5 0x501f48 in AtEOXact_GUC (isCommit=-86 '', nestLevel=84) at guc.c:3907

> This looks like maybe a corrupted stack - the args to AtEOXact_GUC at
> that location in xact.c are hardwired.

No, that's just a fairly typical behavior of debugging with -O greater
than zero --- the registers holding those parameter values got recycled
for something else. This is a rather old version of gdb and it doesn't
always print <<value optimized away>> when it should.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-01-23 21:40:40 Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.
Previous Message Andres Freund 2010-01-23 21:32:14 Re: commit fests