From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2987 invoked by alias); 12 Aug 2013 15:53:47 -0000 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 Received: (qmail 2975 invoked by uid 89); 12 Aug 2013 15:53:46 -0000 X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 12 Aug 2013 15:53:45 +0000 Received: by mail-vc0-f173.google.com with SMTP id id13so2905238vcb.4 for ; Mon, 12 Aug 2013 08:53:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.145.132 with SMTP id d4mr6748317vcv.9.1376322824161; Mon, 12 Aug 2013 08:53:44 -0700 (PDT) Received: by 10.220.53.132 with HTTP; Mon, 12 Aug 2013 08:53:44 -0700 (PDT) In-Reply-To: References: Date: Mon, 12 Aug 2013 15:53:00 -0000 Message-ID: Subject: Re: [PATCH 4/5] powerpc64-aix ptrace64 when defined. From: David Edelsohn To: Raunaq 12 Cc: GDB Patches , Mark Kettenis , Ulrich Weigand Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-08/txt/msg00319.txt.bz2 On Mon, Aug 12, 2013 at 8:00 AM, Raunaq 12 wrote: > The earlier version of this patch was using ptrace64 only if BFD64 was > defined, > i.e. when GDB was built in 64 BIT mode. > Did you build 32 bit gdb? > If so, according to the previous version of this patch, > no ptrace related calls were changed as ptrace64 was only > called if BFD64 was defined. Could you please resend the error you got > while debugging > 32 bit GCC to my mail id? I can look into it to see where the problem is > coming from. I have not tried to build GDB with the latest test of patches. When I used the earlier patches to build GDB in 32 bit mode but with --enable-64-bit-bfd (because I want to debug 64 bit applications), and tried to use the debugger with GCC, I encountered the problem that no function call argument values were available. Thanks, David