public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] -Wwrite-strings: More fix-old-Python-API wrappers
Date: Thu, 06 Apr 2017 00:12:00 -0000	[thread overview]
Message-ID: <4d75997912d77497fd395fde222513436a7df046@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 4d75997912d77497fd395fde222513436a7df046 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4d75997912d77497fd395fde222513436a7df046

-Wwrite-strings: More fix-old-Python-API wrappers

When building against Python 2.7, -Wwrite-strings flags several cases
of passing a string literal to Python functions that expect a "char
*".  This commit addresses the issue like we already handle several
other similar cases -- wrap the Python API with our own fixed
version that adds the necessary constification.

gdb/ChangeLog:
2017-04-05  Pedro Alves  <palves@redhat.com>

	* python/python-internal.h (gdb_PyObject_CallMethod)
	(gdb_PyErr_NewException, gdb_PySys_GetObject, gdb_PySys_SetPath):
	New functions.
	(GDB_PYSYS_SETPATH_CHAR, PyObject_CallMethod, PyErr_NewException)
	(PySys_GetObject, PySys_SetPath): New macros.


             reply	other threads:[~2017-04-06  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  0:12 sergiodj+buildbot [this message]
2017-04-06  0:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-04-06  6:38 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-04-06 10:12 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-04-06 10:35 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-04-06 10:58 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-08-14  4:42 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-08-14  6:37 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2017-08-14 16:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot

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=4d75997912d77497fd395fde222513436a7df046@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).