From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: agrambot@gmail.com, emacs-devel@gnu.org
Subject: Re: Errors building from master with a clean repository
Date: Sat, 20 Apr 2019 09:48:26 +0300 [thread overview]
Message-ID: <83o951b29x.fsf@gnu.org> (raw)
In-Reply-To: <7db3cae7-794c-83d6-b8f4-f0ec000d1674@cs.ucla.edu> (message from Paul Eggert on Fri, 19 Apr 2019 18:05:35 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 19 Apr 2019 18:05:35 -0700
> Cc: emacs-devel@gnu.org
>
> > ./configure --enable-checking=all --enable-check-lisp-object-type \
> > CFLAGS='-Og -gdwarf-4'
>
> --enable-checking=all hasn't worked for a while. Although your email prompted me
> to write and install patches to fix multiple bugs in this area, the remaining
> buggy suboptions --enablechecking=conslist and --enable-checking=xmallocoverrun
> are more trouble than they're worth to fix, and should go. (GCC's
> AddressSanitizer has made both options obsolete anyway.) Please try the two
> attached patches and then try the above 'configure' line again.
If we remove these options, let's have reasonably detailed
instructions for how to use the alternatives. Because this, for
example:
> ++++
> +** The configure option '--enable-checking=conslist' has been withdrawn.
> +It made Emacs irredeemably slow, and is no longer useful with modern
> +debugging tools.
is not detailed enough to be useful, unless one is already an expert
in using the modern debugging tools. Can we please at least mention
specific compiler options and any other tools that could be used
instead of the built-in facilities we are removing? Bonus points for
adding to etc/DEBUG a section with more details about the compiler
options, tools, and techniques of using them for debugging specific
Emacs problems for which these configure options were introduced.
Thanks.
next prev parent reply other threads:[~2019-04-20 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 19:21 Errors building from master with a clean repository Alex Gramiak
2019-04-20 1:05 ` Paul Eggert
2019-04-20 6:48 ` Eli Zaretskii [this message]
2019-04-22 6:22 ` Paul Eggert
2019-04-22 7:45 ` Eli Zaretskii
2019-04-23 0:31 ` Paul Eggert
2019-04-23 6:05 ` Eli Zaretskii
2019-04-20 16:10 ` Alex Gramiak
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o951b29x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).