From: Phil Muldoon <pmuldoon@redhat.com>
To: Ken Werner <ken@linux.vnet.ibm.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Add solib_address and decode_line Python functionality
Date: Fri, 13 Aug 2010 14:14:00 -0000 [thread overview]
Message-ID: <4C65533B.5000006@redhat.com> (raw)
In-Reply-To: <201008131607.09618.ken@linux.vnet.ibm.com>
On 13/08/10 15:07, Ken Werner wrote:
> On Tuesday, August 10, 2010 08:24:09 pm Tom Tromey wrote:
>>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>> Tom> So, could you make this conditional?
>>
>> Phil> Sure, what do you think of the attached patch?
>>
>> Thanks for persevering. This is ok.
>
> Hi,
>
> It looks like the const qualifier of the format string argument of the
> PyArg_Parse* routines has been introduced after the Python 2.4 release:
> http://svn.python.org/view?view=rev&revision=41638
> In case gdb is built against libpython 2.4 the current code would generate a
> warning. One solution would be to just remove the const qualifier. A small
> patch is attached. Any comments are appreciated.
Thanks for catching this. It looks fine to me; but wait for Tom or
another maintainer to give the official nod first.
Cheers
Phil
next prev parent reply other threads:[~2010-08-13 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:43 Phil Muldoon
2010-07-27 16:26 ` Joel Brobecker
2010-07-28 11:35 ` Phil Muldoon
2010-07-28 17:39 ` Joel Brobecker
2010-07-28 17:48 ` Eli Zaretskii
2010-07-29 20:39 ` Tom Tromey
2010-08-06 13:55 ` Phil Muldoon
2010-08-06 15:36 ` Eli Zaretskii
2010-08-06 22:39 ` Tom Tromey
2010-08-10 11:17 ` Phil Muldoon
2010-08-10 17:07 ` Eli Zaretskii
2010-08-10 18:24 ` Tom Tromey
2010-08-11 13:16 ` Phil Muldoon
2010-08-13 14:07 ` Ken Werner
2010-08-13 14:14 ` Phil Muldoon [this message]
2010-08-13 15:48 ` Tom Tromey
2010-08-13 16:22 ` Ken Werner
2010-08-18 23:55 ` Pedro Alves
2010-08-19 16:32 ` Tom Tromey
2010-08-19 17:04 ` Pedro Alves
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=4C65533B.5000006@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ken@linux.vnet.ibm.com \
--cc=tromey@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).