Re: [HACKERS] pg_user crash

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] pg_user crash
Date: 1998-09-11 01:27:59
Message-ID: 35F87C9F.C66EACF4@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
>
> OK, I have a way to debug this.
>
> Add to palloc and pfree a printf like:
>
> printf("palloc: %d\n", mem);
> printf("pfree : %d\n", mem);
>
> The printf's should go after the memory is allocated in palloc, and
> before it is free'ed in pfree().
>
> and then run the backend and issue the query causing the problem, and
> grab the lines from the postmaster log file. Check the last pfree
> value, because that is the one that is crashing it. Check the list to
> see if it has been palloc'ed. If it has, was it pfree'ed by someone
> else, and who palloc'ed it. If it is not on the list, figure out how it
> got on to the palloc list.

Crash comes from AllocSetReset()->AllocSetFree() - printf in
pfree will not help.

I would suggest to add printf to AllocSetFree()/AllocSetAlloc()...

Vadim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Midwest Online 1998-09-11 05:11:17 getting "fe_setauthsvc: invalid name" error
Previous Message Bruce Momjian 1998-09-10 23:47:40 Re: [HACKERS] regression test errors: netbsd 1.3.2/i386