Re: Current CVS tip segfaulting - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Current CVS tip segfaulting
Date
Msg-id 7717.1082782611@sss.pgh.pa.us
Whole thread Raw
In response to Re: Current CVS tip segfaulting  (Alvaro Herrera Munoz <alvherre@dcc.uchile.cl>)
List pgsql-hackers
Alvaro Herrera Munoz <alvherre@dcc.uchile.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: contrib vs. gborg/pgfoundry for replication solutions
Next
From: Shachar Shemesh
Date:
Subject: Do we prefer software that works or software that looks good?