From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4347 invoked by alias); 14 May 2012 03:10:00 -0000 Received: (qmail 4334 invoked by uid 22791); 14 May 2012 03:09:59 -0000 X-SWARE-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 May 2012 03:09:46 +0000 Received: by qcsd16 with SMTP id d16so3620262qcs.0 for ; Sun, 13 May 2012 20:09:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-system-of-record:x-gm-message-state; bh=9g3G0cNdPub1m6qUlC6/LMKbGems3zKL8TQ0vL2iS4U=; b=nsJd1olQoodoF2rkabIIYyyNqYcl8Au/jKNFPbWZHz0r5Kr67YSpzlKazGYs2VqjUn HwGPcqYzGDbiC5QGeDSbkjGo5TRTV/2G4RMhFLxk59vMMbyPqwbRIzxg1T5inVfraorx JRI94l4IJNNaxZhmUKOhSaxLPPCksmQ/8WGZJnhtW5Wwd6ge+aTBqE1LJmQvweYSIMuU /dLCaO4AqfbMFsW/mPD0BG+gsT3+U9JqrIE+BZX3fVwtob7xL5DxOj69iUH4dX7oLh+u fqUBO+VeVGFlcmfe/qZ1FO2JDxRilGhWsYhyvhU4QSlL6RZpEtA3gfkC59FUr1DVjEgM gh0g== Received: by 10.229.135.141 with SMTP id n13mr3172880qct.25.1336964986082; Sun, 13 May 2012 20:09:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.135.141 with SMTP id n13mr3172874qct.25.1336964985934; Sun, 13 May 2012 20:09:45 -0700 (PDT) Received: by 10.224.215.132 with HTTP; Sun, 13 May 2012 20:09:45 -0700 (PDT) In-Reply-To: <20120514015548.GA27497@sourceware.org> References: <20120514015548.GA27497@sourceware.org> Date: Mon, 14 May 2012 03:10:00 -0000 Message-ID: Subject: Re: New ARI warning Mon May 14 01:55:48 UTC 2012 From: Siva Chandra To: gdb-patches@sourceware.org Content-Type: multipart/mixed; boundary=e0cb4e59348a10566204bff66b2e X-System-Of-Record: true X-Gm-Message-State: ALoCoQnKkeSGqGwbQCInNZRV4qkFtdrEdVbIHzTaP6Ly/nCocjRHZolwjhxaTevOUw+l6d4Wy/YhFGHRa0IXSySGTSFmfwKbyeH0k4Z/09nzPaVmM4cYKyA3lk24eOWbLWVW7UImEWjycRgpT7khjgd0HMIbQ6K/9Q== 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-05/txt/msg00497.txt.bz2 --e0cb4e59348a10566204bff66b2e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-length: 478 On Mon, May 14, 2012 at 7:25 AM, GDB Administrator wrote: > 719a720 >> gdb/python/python.c:642: code: long long: Do not use 'long long', instea= d use LONGEST > gdb/python/python.c:642: =A0unsigned long long pc_llu; Committed the attached patch as obvious to fix this. 2012-05-14 Siva Chandra Reddy * python/python.c (gdbpy_find_pc_line): Use ULONGEST instead of unsigned long long. Thanks, Siva Chandra --e0cb4e59348a10566204bff66b2e Content-Type: text/plain; charset=US-ASCII; name="ari_fix.txt" Content-Disposition: attachment; filename="ari_fix.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h26yenmg0 Content-length: 716 SW5kZXg6IHB5dGhvbi9weXRob24uYwo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 ClJDUyBmaWxlOiAvY3ZzL3NyYy9zcmMvZ2RiL3B5dGhvbi9weXRob24uYyx2 CnJldHJpZXZpbmcgcmV2aXNpb24gMS44NwpkaWZmIC11IC1wIC1yMS44NyBw eXRob24uYwotLS0gcHl0aG9uL3B5dGhvbi5jCTEzIE1heSAyMDEyIDExOjMz OjQzIC0wMDAwCTEuODcKKysrIHB5dGhvbi9weXRob24uYwkxNCBNYXkgMjAx MiAwMzowNTozMiAtMDAwMApAQCAtNjM5LDcgKzYzOSw3IEBAIGdkYnB5X2Zp bmRfcGNfbGluZSAoUHlPYmplY3QgKnNlbGYsIFB5T2IKIHsKICAgc3RydWN0 IHN5bXRhYl9hbmRfbGluZSBzYWw7CiAgIENPUkVfQUREUiBwYzsKLSAgdW5z aWduZWQgbG9uZyBsb25nIHBjX2xsdTsKKyAgVUxPTkdFU1QgcGNfbGx1Owog CiAgIGlmICghUHlBcmdfUGFyc2VUdXBsZSAoYXJncywgR0RCX1BZX0xMVV9B UkcsICZwY19sbHUpKQogICAgIHJldHVybiBOVUxMOwo= --e0cb4e59348a10566204bff66b2e--