From: Uwe Brauer <oub@mat.ucm.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
Subject: Re: git+master: c6e6503900534d939dd94b812563c27f22c49b7d crash when using gnus
Date: Sun, 29 Apr 2018 10:46:42 +0200 [thread overview]
Message-ID: <87vaca2ydp.fsf@mat.ucm.es> (raw)
In-Reply-To: 83a7tnttw9.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>>
>> CFLAGS='-O0 -g3' ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type
> Yes, that's a good beginning.
This dos not work. That description most likely is incomplete.
On the prompt that line gives error, so I presume that CFLAGS='-O0 -g3'
is a setting either in bash or tcsh shell.
Can you please tell me precisely how this setting should work, and may I
recommend change it in the documentation. Once I have finished
successfully the compilation and the debugging I don't mind doing that.
It might be that for experts like you these things are obvious, for a
C debugging beginner like me, they are not.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2018-04-29 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 9:06 git+master: c6e6503900534d939dd94b812563c27f22c49b7d crash when using gnus Uwe Brauer
2018-04-28 9:43 ` Eli Zaretskii
2018-04-28 10:11 ` Uwe Brauer
2018-04-28 10:46 ` Eli Zaretskii
2018-04-28 11:56 ` Uwe Brauer
2018-04-28 12:09 ` Eli Zaretskii
2018-04-29 8:46 ` Uwe Brauer [this message]
2018-04-29 9:53 ` Eli Zaretskii
2018-04-29 14:54 ` Uwe Brauer
2018-04-29 15:09 ` Eli Zaretskii
2018-04-29 15:26 ` Noam Postavsky
2018-04-29 16:30 ` Paul Eggert
2018-04-29 17:08 ` Eli Zaretskii
2018-04-29 17:18 ` Paul Eggert
2018-04-29 17:40 ` Eli Zaretskii
2018-04-29 16:31 ` Eli Zaretskii
2018-04-29 15:01 ` Uwe Brauer
2018-04-29 15:33 ` Noam Postavsky
2018-04-29 16:33 ` Eli Zaretskii
2018-04-29 16:39 ` Uwe Brauer
2018-04-29 16:39 ` Uwe Brauer
2018-04-29 17:09 ` Eli Zaretskii
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=87vaca2ydp.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=eliz@gnu.org \
--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).