According to the backtrace, it appears to be dieing in malloc.
#0 0x40149f9c in _int_malloc () from /lib/i686/libc.so.6
#1 0x40149201 in malloc () from /lib/i686/libc.so.6
#2 0x080547c3 in mm_alloc (size=3) at type.c:13
#3 0x080493a0 in make_str (str=0x4020c400 "\001") at preproc.y:129
#4 0x0804f629 in yyparse () at preproc.y:4899
#5 0x08055db0 in main (argc=2, argv=0xbfffdb94) at ecpg.c:424
#6 0x400eba67 in __libc_start_main () from /lib/i686/libc.so.6
Michael Fuhr wrote:
>On Mon, Jan 24, 2005 at 12:08:36PM -0700, Michael Fuhr wrote:
>>ecpg in free(): warning: chunk is already free
>>If you have a core dump then maybe you can do a backtrace and see
>>where that's happening.
>This assumes, perhaps prematurely, that the free() problem is causing
>the core dump on your platform. In any case, a backtrace should
>help track down the problem.
Edmund Bacon <ebacon(at)onesystem(dot)com>
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2005-01-24 20:03:37|
|Subject: Re: BUG #1440: ecpg seg faults |
|Previous:||From: Tom Lane||Date: 2005-01-24 19:24:54|
|Subject: Re: BUG #1433: domain check constraint not checked when adding new column |