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: Tue, 23 Apr 2019 09:05:23 +0300 [thread overview]
Message-ID: <838sw15k9o.fsf@gnu.org> (raw)
In-Reply-To: <84279731-9572-de3c-4806-a7c52fb79fee@cs.ucla.edu> (message from Paul Eggert on Mon, 22 Apr 2019 17:31:44 -0700)
> Cc: agrambot@gmail.com, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 22 Apr 2019 17:31:44 -0700
>
> No, I was merely assuming that -gdwarf-4 is good enough to debug Emacs;
> -gdwarf-5 is still marked as "experimental" in GCC 8's doc, and I
> haven't used -gdwarf-5. If there's a significant advantage to using
> -gdwarf-5 then discussion of it should be added to etc/DEBUG. In the
> meantime I tried to improve the wording about this, in the attached patch.
>
>
> > I think this section could greatly benefit from a short explanation
> > what "undefined behavior" means, or a couple of examples of it.
>
> It's hard to be brief as -fsanitize=undefined is a bit tricky, but I
> took a shot at it by installing the attached.
Thanks, these are very useful additions, IMO.
next prev parent reply other threads:[~2019-04-23 6:05 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
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 [this message]
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=838sw15k9o.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).