Re: OSX doesn't accept identical source/target for strcpy() anymore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Matthias Schmitt <freak002(at)mmp(dot)lu>
Subject: Re: OSX doesn't accept identical source/target for strcpy() anymore
Date: 2013-10-28 16:28:47
Message-ID: 5091.1382977727@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> There have been previous discussions about fixing strcpy calls with
> identical source/destination (same for memcpy) but it was deemed not
> worth the effort. I don't really see an alternative to fixing it now.

I'm not seeing this with bare-bones

./configure --enable-debug --enable-cassert

on an OS X Mavericks machine with Xcode downloaded today. So there
is something unidentified as yet about Matthias's configuration.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2013-10-28 16:31:26 Re: OSX doesn't accept identical source/target for strcpy() anymore
Previous Message Andres Freund 2013-10-28 16:26:52 Re: Darwin: make check fails with "child process exited with exit code 134"

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-10-28 16:31:26 Re: OSX doesn't accept identical source/target for strcpy() anymore
Previous Message Robert Haas 2013-10-28 16:28:46 Re: logical changeset generation v6.2