Skip site navigation (1) Skip section navigation (2)

Re: BUG #1440: ecpg seg faults

From: Edmund Bacon <ebacon(at)onesystem(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1440: ecpg seg faults
Date: 2005-01-24 19:24:57
Message-ID: 41F54B89.8030302@onesystem.com (view raw or flat)
Thread:
Lists: pgsql-bugs
According to the backtrace, it appears to be dieing in malloc.

(gdb) bt
#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
(gdb)

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

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-01-24 20:03:37
Subject: Re: BUG #1440: ecpg seg faults
Previous:From: Tom LaneDate: 2005-01-24 19:24:54
Subject: Re: BUG #1433: domain check constraint not checked when adding new column

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group