Re: Crash during elog.c... - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Crash during elog.c...
Date
Msg-id 200511042134.jA4LYZf15136@candle.pha.pa.us
Whole thread Raw
In response to Re: Crash during elog.c...  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: Crash during elog.c...  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
Jim C. Nasby wrote:
> On Fri, Nov 04, 2005 at 02:45:41PM -0500, Tom Lane wrote:
> > "Jim C. Nasby" <jnasby@pervasive.com> writes:
> > > The backtrace:
> > > Program terminated with signal 11, Segmentation fault.
> > > (gdb) bt
> > > #0  0x0000003b8946fb20 in strlen () from /lib64/tls/libc.so.6
> > > #1  0x0000003b894428dc in vfprintf () from /lib64/tls/libc.so.6
> > > #2  0x0000003b89461ba4 in vsnprintf () from /lib64/tls/libc.so.6
> > > #3  0x00000000004ff420 in appendStringInfoVA (str=0x7fbfffde30, fmt=0x65f59e "%s", args=0x7fbfffdb50) at
stringinfo.c:125
> > 
> > Hrm ... what's the platform again?
> 
> 8-way opteron, RHEL4.
> 
> BTW, should I be opening bugs for things like this? I guess I probably
> should...

Nope, reporting it here is fine.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Assert failure found in 8.1RC1
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Exclusive lock for database rename