From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2075 invoked by alias); 14 Mar 2003 20:19:19 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2020 invoked from network); 14 Mar 2003 20:19:18 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 14 Mar 2003 20:19:18 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 79F6D2B11; Fri, 14 Mar 2003 15:19:06 -0500 (EST) Message-ID: <3E72393A.9080904@redhat.com> Date: Fri, 14 Mar 2003 20:19:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Elena Zannoni Cc: gdb-patches@sources.redhat.com, mludvig@suse.cz Subject: Re: [PATCH] x86-64 fixes References: <15986.3469.893786.554687@localhost.redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00336.txt.bz2 > It also fixes some calls to malloc() failures. These were evident in > tests that do stuff like p "foo" or p str_func ("foo") or even simple > calls like p malloc(2). Outch! A working ``(gdb) p malloc(...)'' is pretty fundmental to a functional GDB. Without it, many of the test results are pretty meaningless. This should definitly help stablize the target. Andrew