Re: [HACKERS] Crash during elog.c...

2005-11-07 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > On Fri, Nov 04, 2005 at 08:06:39PM -0500, Tom Lane wrote: >> Um, what's your log_line_prefix setting, and is the next format code >> %i by any chance? I've just noticed an utterly brain-dead assumption >> somebody stuck into ps_status.c awhile back. >

Re: [HACKERS] Crash during elog.c...

2005-11-07 Thread Jim C. Nasby
On Fri, Nov 04, 2005 at 08:06:39PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > My client (same one with the slru.c issue) has had 3 of these in the > > past day... > > > (gdb) print *str > > $39 = {data = 0x848030 "2005-11-04 00:01:02 EST|2005-11-04 00:00:08 > > EST|21

Re: [HACKERS] Crash during elog.c...

2005-11-04 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > My client (same one with the slru.c issue) has had 3 of these in the > past day... > (gdb) print *str > $39 = {data = 0x848030 "2005-11-04 00:01:02 EST|2005-11-04 00:00:08 > EST|216.187.113.78(39476)|didit|", len = 76, > maxlen = 256, cursor = 0} Um

Re: [HACKERS] Crash during elog.c...

2005-11-04 Thread Jim C. Nasby
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" <[EMAIL PROTECTED]> writes: > > > > The backtrace: > > > > Program terminated with signal 11, Segmentation fault. > > > > (gdb) bt

Re: [HACKERS] Crash during elog.c...

2005-11-04 Thread Bruce Momjian
Jim C. Nasby wrote: > On Fri, Nov 04, 2005 at 02:45:41PM -0500, Tom Lane wrote: > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > > The backtrace: > > > Program terminated with signal 11, Segmentation fault. > > > (gdb) bt > > > #0 0x003b8946fb20 in strlen () from /lib64/tls/libc.so.6 > > > #

Re: [HACKERS] Crash during elog.c...

2005-11-04 Thread Jim C. Nasby
On Fri, Nov 04, 2005 at 02:45:41PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > The backtrace: > > Program terminated with signal 11, Segmentation fault. > > (gdb) bt > > #0 0x003b8946fb20 in strlen () from /lib64/tls/libc.so.6 > > #1 0x003b894428dc in vfprintf

Re: [HACKERS] Crash during elog.c...

2005-11-04 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > The backtrace: > Program terminated with signal 11, Segmentation fault. > (gdb) bt > #0 0x003b8946fb20 in strlen () from /lib64/tls/libc.so.6 > #1 0x003b894428dc in vfprintf () from /lib64/tls/libc.so.6 > #2 0x003b89461ba4 in vsnprintf ()

[HACKERS] Crash during elog.c...

2005-11-04 Thread Jim C. Nasby
My client (same one with the slru.c issue) has had 3 of these in the past day... The backtrace: Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x003b8946fb20 in strlen () from /lib64/tls/libc.so.6 #1 0x003b894428dc in vfprintf () from /lib64/tls/libc.so.6 #2 0x00