From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add support for --enable-lmcheck configure option.
Date: Tue, 12 Jun 2012 07:42:00 -0000 [thread overview]
Message-ID: <20120612074215.GB4374@host2.jankratochvil.net> (raw)
In-Reply-To: <1339447127-314-1-git-send-email-brobecker@adacore.com>
Hi Joel,
On Mon, 11 Jun 2012 22:38:47 +0200, Joel Brobecker wrote:
> This allows the user to enable this option at configure time if building
> a release,
[...]
> It might be useful
> later on, when debugging memory problems on a release version of GDB.
this is bloating the configure script + configure help. Just use:
LDFLAGS=-lmcheck ./configure ...
> I don't think I'll personally use the --disable-libmcheck on a snapshot,
> but someone distributing a snaphot version might enjoy it too.
Yes:
http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-disable-mcheck.patch;hb=master
But I do not find it so important to make a configure option to it.
> OK?
Given that --disable-libmcheck for snapshot may make some sense I do not
oppose it but I do not think it is worth it, it is a corner case where one can
edit configure or Makefile IMO.
I understand the reason is to workaround current GDB bugs exposed by -lmcheck.
This is sure not the right solution.
Regards,
Jan
next prev parent reply other threads:[~2012-06-12 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 20:39 Joel Brobecker
2012-06-12 7:42 ` Jan Kratochvil [this message]
2012-06-12 16:55 ` Joel Brobecker
2012-06-12 17:00 ` Jan Kratochvil
2012-07-25 18:39 ` Joel Brobecker
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=20120612074215.GB4374@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.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