Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44EF5492.10008@roguewave.com>
Date: Fri, 25 Aug 2006 13:50:42 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: [patch] Exec utility memory leak fix
References: <44E64778.8010507@roguewave.com> <44EA5B8D.40800@roguewave.com>
 <44EF31FC.2050304@roguewave.com>
In-Reply-To: <44EF31FC.2050304@roguewave.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Andrew Black wrote:
> Greetings Martin.
> 
> I think the problem is that the Solaris patch utility has problems with 
> whitespace fuzz (specifically with changes in trailing whitespace).

I figured it had something to do with whitespace.

> 
> When I pulled your attached copy of the patch and applied it (on my 
> linux box), I recieved the following message:
> 
> [ablack@quandry util]$ patch < leakfix.diff
> patching file runall.cpp
> Hunk #1 succeeded at 73 with fuzz 1.

I wonder if the spaces might have been introduced into the text
of the patch by one of our mailers or by ezmlm. It might be best
to avoid pasting patches into email and instead attach them as
files.

Martin