From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16836 invoked by alias); 29 Nov 2006 15:24:48 -0000 Received: (qmail 16826 invoked by uid 22791); 29 Nov 2006 15:24:46 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 29 Nov 2006 15:24:39 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1GpRIb-0000Ge-Db; Wed, 29 Nov 2006 10:24:37 -0500 Date: Wed, 29 Nov 2006 15:24:00 -0000 From: Daniel Jacobowitz To: Nathan Sidwell Cc: gdb-patches@sourceware.org Subject: Re: adjust linux-dp test Message-ID: <20061129152437.GA847@nevyn.them.org> Mail-Followup-To: Nathan Sidwell , gdb-patches@sourceware.org References: <456DA000.6030908@codesourcery.com> <20061129150752.GW30862@caradoc.them.org> <456DA3EA.5020001@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <456DA3EA.5020001@codesourcery.com> User-Agent: Mutt/1.5.13 (2006-08-11) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00392.txt.bz2 On Wed, Nov 29, 2006 at 03:14:50PM +0000, Nathan Sidwell wrote: > Daniel Jacobowitz wrote: > >On Wed, Nov 29, 2006 at 02:58:08PM +0000, Nathan Sidwell wrote: > >>My recent change to linux-dp.exp wasn't robust because (a) some thread > >>ids can be negative numbers and (b) sometimes you'd get a 'cannot access > >>memory' error in printing out a prototype, and that would mess up the \n > >>placement. > > > >When does (b) happen? That's strange. > > for example here ... > info threads > 3 Thread -1218434144 (LWP 2749) 0xffffe410 in __kernel_vsyscall () > 2 Thread -1210037344 (LWP 2748) 0xffffe410 in __kernel_vsyscall () > * 1 Thread -1210034512 (LWP 2745) main (argc=Cannot access memory at > address 0x0 > ) at ../../../src/gdb/testsuite/gdb.threads/linux-dp.c:189 Well that's totally lame. I don't see how it happens, either, I'd expect the error in val_print to catch it. I think you need to allow newlines in this output anyway; it might wrap printing many parameters of a function. So may as well just relax the error for now. -- Daniel Jacobowitz CodeSourcery