Geoffrey <esoteric@3times25.net> writes:
> Tom Lane wrote:
>> Please provide a stack trace from that coredump ...
> It follows. Note, the references to /usr/local/pcm170/... are from a
> 3rd party application we have built into our backend. I'm sure I know
> what I'll hear regarding that issue. :) We are in the process up
> upgrading to a newer version of this product. stack trace follows:
> #0 0x001968a4 in vfprintf () from /lib/tls/libc.so.6
> #1 0x001b7d24 in vsnprintf () from /lib/tls/libc.so.6
> #2 0x0019d0a4 in snprintf () from /lib/tls/libc.so.6
> #3 0x002d29c2 in pcm_getmiles_s () from /esc/pgrnd/prog/libpcmiler.so
> #4 0x081082c4 in ExecMakeFunctionResult ()
Looks to me like pcm_getmiles_s is passing a bad pointer to snprintf,
or perhaps providing an insufficiently large output buffer. You'll
need to take it up with the author of that function --- it's highly
unlikely that this is a bug in the core Postgres code.
regards, tom lane