Re: Crash during elog.c...

On Fri, Nov 04, 2005 at 04:34:35PM -0500, Bruce Momjian wrote:
> 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.

I'm soon to be AFK all weekend... is there any more info anyone wanted
about this?
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461