From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: Hui Zhu <teawater@gmail.com>, gdb-patches@sourceware.org
Subject: [patch] Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
Date: Thu, 30 Aug 2012 16:43:00 -0000 [thread overview]
Message-ID: <20120830164317.GA27381@host2.jankratochvil.net> (raw)
In-Reply-To: <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu>
On Thu, 30 Aug 2012 18:00:46 +0200, Khoo Yit Phang wrote:
> 2012-08-30 Khoo Yit Phang <khooyp@cs.umd.edu>
This patch does not seem to require copyright assignment but it would be safer
to complete one for example from Sergio Durigan Junior <sergiodj@redhat.com>.
Also for any possible future contributions.
> Disable -lmcheck when Python is enabled with threading support.
> * configure.ac: Move --enable-lmcheck after --with-python, and
> disable if python_has_threads=yes.
Describe it more technically, new variable python_has_threads, check
${python_prog} --has-threads etc.
[...]
> +# Provide a --enable-libmcheck/--disable-libmcheck set of options
> +# allowing a user to enable this option even when building releases,
> +# or to disable it when building a snapshot.
> +AC_ARG_ENABLE(libmcheck,
> + AS_HELP_STRING([--enable-libmcheck],
> + [Try building GDB with -lmcheck if available]),
> + [case "${enableval}" in
> + yes | y) ENABLE_LIBMCHECK="yes" ;;
> + no | n) ENABLE_LIBMCHECK="no" ;;
> + *) AC_MSG_ERROR(bad value ${enableval} for --enable-libmcheck) ;;
> + esac])
> +
> +# Enable -lmcheck by default (it provides cheap-enough memory mangling),
> +# but turn it off for releases.
> +if test -z "${ENABLE_LIBMCHECK}" && $development; then
> + ENABLE_LIBMCHECK=yes
> +fi
> +
> +if test "$ENABLE_LIBMCHECK" = "yes" ; then
> + if test "${have_libpython}" != "no" -a "${python_has_threads}" = "yes" ; then
> + AC_MSG_WARN(libmcheck disabled since python has threads)
> + else
> + AC_CHECK_LIB(mcheck, main)
> + fi
> +fi
I am fine with this goal of disabling -lmcheck by default (when
--enable-libmcheck was not specified) when threaded libpython is linked in.
But when user explicitly specifies --enable-libmcheck it should give the
warning but still enable libmcheck. In most of the uses of GDB libmcheck is
safe with GDB.
> --- a/gdb/python/python-config.py
> +++ b/gdb/python/python-config.py
> @@ -1,5 +1,5 @@
> # Program to fetch python compilation parameters.
> -# Copied from python-config of the 2.7 release.
> +# Copied from python-config of the 2.7 release, modified to test for threads.
Please submit it also for Python. The commit in GDB sources is OK as long as
it gets imported by upstream Python. They may also suggest some other
solution if they do not agree with this one.
Thanks for catching it.
Jan
next parent reply other threads:[~2012-08-30 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANFwon0wEXd+40H85veHyRTg+itYyL2jjgsCMYByxk5K0MTLHA@mail.gmail.com>
[not found] ` <20120719073959.GA10044@host2.jankratochvil.net>
[not found] ` <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu>
2012-08-30 16:43 ` Jan Kratochvil [this message]
2012-08-30 18:05 ` Khoo Yit Phang
2012-08-30 18:21 ` Jan Kratochvil
2012-08-30 18:58 ` Khoo Yit Phang
2012-08-30 19:05 ` Jan Kratochvil
2012-08-30 19:28 ` Khoo Yit Phang
2012-08-31 1:32 ` Khoo Yit Phang
2012-08-31 8:14 ` Jan Kratochvil
2012-08-31 15:30 ` Khoo Yit Phang
2012-08-31 15:41 ` Andreas Schwab
2012-08-31 16:08 ` Khoo Yit Phang
2012-08-31 17:02 ` Andreas Schwab
2012-08-31 18:03 ` Khoo Yit Phang
2012-08-31 18:23 ` Jan Kratochvil
2012-08-31 18:41 ` Khoo Yit Phang
2012-09-02 15:37 ` Jan Kratochvil
2012-09-06 19:31 ` Khoo Yit Phang
2012-08-30 18:22 ` Sergio Durigan Junior
2012-08-30 18:45 ` Khoo Yit Phang
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=20120830164317.GA27381@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
--cc=teawater@gmail.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