Re: Current CVS tip segfaulting

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Current CVS tip segfaulting
Date: 2004-04-24 04:56:51
Message-ID: 7717.1082782611@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> [ bug goes away if ]
> ! dbname = argv[optind];
> [becomes]
> ! dbname = pstrdup(argv[optind]);

Hm, that's interesting. I could believe this would have something to do
with overwriting the argv area, but we have not touched any of that code
recently; so why would it break for you just now?

Which PS_USE_FOO option does your platform use? (See
src/backend/utils/misc/ps_status.c)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shachar Shemesh 2004-04-24 05:23:57 Do we prefer software that works or software that looks good?
Previous Message Tom Lane 2004-04-24 04:42:26 Re: contrib vs. gborg/pgfoundry for replication solutions