Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: gdb-patches@sourceware.org
Subject: Re: New ARI warning Mon May 14 01:55:48 UTC 2012
Date: Mon, 14 May 2012 03:10:00 -0000	[thread overview]
Message-ID: <CAGyQ6gwE9ETtDhmutt+PieVvU7NpUgYuN0-TD+be6fDmgtFvOQ@mail.gmail.com> (raw)
In-Reply-To: <20120514015548.GA27497@sourceware.org>

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

On Mon, May 14, 2012 at 7:25 AM, GDB Administrator
<gdbadmin@sourceware.org> wrote:
> 719a720
>> gdb/python/python.c:642: code: long long: Do not use 'long long', instead use LONGEST
> gdb/python/python.c:642:  unsigned long long pc_llu;

Committed the attached patch as obvious to fix this.

2012-05-14  Siva Chandra Reddy  <sivachandra@google.com>

        * python/python.c (gdbpy_find_pc_line): Use ULONGEST instead of
        unsigned long long.


Thanks,
Siva Chandra

[-- Attachment #2: ari_fix.txt --]
[-- Type: text/plain, Size: 527 bytes --]

Index: python/python.c
===================================================================
RCS file: /cvs/src/src/gdb/python/python.c,v
retrieving revision 1.87
diff -u -p -r1.87 python.c
--- python/python.c	13 May 2012 11:33:43 -0000	1.87
+++ python/python.c	14 May 2012 03:05:32 -0000
@@ -639,7 +639,7 @@ gdbpy_find_pc_line (PyObject *self, PyOb
 {
   struct symtab_and_line sal;
   CORE_ADDR pc;
-  unsigned long long pc_llu;
+  ULONGEST pc_llu;
 
   if (!PyArg_ParseTuple (args, GDB_PY_LLU_ARG, &pc_llu))
     return NULL;

  reply	other threads:[~2012-05-14  3:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  1:56 GDB Administrator
2012-05-14  3:10 ` Siva Chandra [this message]
2012-05-14 20:33   ` Tom Tromey
2012-05-15 20:26     ` Tom Tromey
2012-05-16  3:12       ` Siva Chandra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGyQ6gwE9ETtDhmutt+PieVvU7NpUgYuN0-TD+be6fDmgtFvOQ@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox