Re: BUG #1440: ecpg seg faults
| От | Edmund Bacon |
|---|---|
| Тема | Re: BUG #1440: ecpg seg faults |
| Дата | |
| Msg-id | 41F54B89.8030302@onesystem.com обсуждение исходный текст |
| Ответ на | Re: BUG #1440: ecpg seg faults (Michael Fuhr <mike@fuhr.org>) |
| Ответы |
Re: BUG #1440: ecpg seg faults
|
| Список | 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@onesystem.com>
В списке pgsql-bugs по дате отправления: