From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2259 invoked by alias); 1 Apr 2003 01:09:46 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2224 invoked from network); 1 Apr 2003 01:09:44 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sources.redhat.com with SMTP; 1 Apr 2003 01:09:44 -0000 Received: (qmail 74293 invoked by uid 20157); 1 Apr 2003 01:09:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Apr 2003 01:09:39 -0000 Date: Tue, 01 Apr 2003 01:09:00 -0000 From: Hans-Peter Nilsson X-X-Sender: hp@dair.pair.com To: Andrew Cagney cc: David Carlton , gdb , Subject: Re: gdb.mi/mi-cli.exp failures In-Reply-To: <3E88B12C.6070609@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-04/txt/msg00000.txt.bz2 On Mon, 31 Mar 2003, Andrew Cagney wrote: > And this: > > > - return concat (filename); > > + return filename; > > (remembering that the patch is backwards) doesn't look so good. It > should be: > > concat (filename, NULL); > > perhaps > > xstrdup (filename) > > would be easier to read :-) \begin{chant} There must be no xstrdup calls in bfd. BFD must not abort; it's a library and the caller must handle allocation failures. There may be xstrdup calls in bfd already, but please don't add new ones. \end{chant} brgds, H-P