Re: pg_dump dumping... core
От | ohp@pyrenet.fr |
---|---|
Тема | Re: pg_dump dumping... core |
Дата | |
Msg-id | Pine.UW2.4.53.0304241929340.1908@server.pyrenet.fr обсуждение исходный текст |
Ответ на | Re: pg_dump dumping... core (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
PLEASE discard my previous mail. I tried append snprintf.o to LIBSOBJ and it did'nt change a thing; crash at the same place. I feel bad!! On Thu, 24 Apr 2003, Tom Lane wrote: > Date: Thu, 24 Apr 2003 10:57:25 -0400 > From: Tom Lane <tgl@sss.pgh.pa.us> > To: ohp@pyrenet.fr > Cc: pgsql-hackers list <pgsql-hackers@postgresql.org> > Subject: Re: [HACKERS] pg_dump dumping... core > > ohp@pyrenet.fr writes: > > pg_dump is crashing on 1 database here. > > Judging from the backtrace, malloc's data structures have gotten > corrupted, probably as a result of somebody scribbling on a few more > bytes than their buffer would hold. > > Since we haven't seen other reports of similar problems, I'm leaning > to the theory that it's a platform-specific problem. In particular > I wonder whether you might have a buggy version of vsnprintf(). I have > seen Solaris 7's vsnprintf() overrun its output buffer --- could > Unixware's have the same bug? > > It'd be worth trying the workaround outlined in FAQ_Solaris (add > snprintf.o to LIBOBJS and rebuild libpq.so), just to see if it makes > any difference. If not, you're in for some tedious debugging to try > to figure out exactly where the culprit is :-( > > regards, tom lane > -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp@pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)
В списке pgsql-hackers по дате отправления: