From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20114 invoked by alias); 2 Jul 2012 17:57:38 -0000 Received: (qmail 20104 invoked by uid 22791); 2 Jul 2012 17:57:37 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-galgo.atl.sa.earthlink.net (HELO elasmtp-galgo.atl.sa.earthlink.net) (209.86.89.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Jul 2012 17:57:24 +0000 Received: from [68.96.200.16] (helo=macbook2.local) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1SlksF-0007wn-UX for gdb-patches@sourceware.org; Mon, 02 Jul 2012 13:57:24 -0400 Message-ID: <4FF1E0FD.1020702@earthlink.net> Date: Mon, 02 Jul 2012 17:57:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: gdb-patches@sourceware.org Subject: Re: [commit] fix gdbserver build failure on amd64-linux References: <20120702171241.5E9E11E1392@ruffy2.mtv.corp.google.com> <87hatqxdpz.fsf@fleche.redhat.com> In-Reply-To: <87hatqxdpz.fsf@fleche.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da940b40e57527c3db472513d62bfad78bd1f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes 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: 2012-07/txt/msg00022.txt.bz2 On 7/2/12 10:41 AM, Tom Tromey wrote: > Doug> - fprintf (stderr, "at 0x%s, bp command_list is 0x%x\n", > Doug> - paddress (where), (int) bp->command_list); > Doug> + fprintf (stderr, "at 0x%s, bp command_list is 0x%lx\n", > Doug> + paddress (where), (long) (uintptr_t) bp->command_list); > > I think it is more normal to use host_address_to_string here. > Or maybe dump the debug print altogether - I'm looking at it and wondering why I ever thought this one was going to be useful. :-) Stan