all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: 13775@debbugs.gnu.org
Subject: bug#13775: 24.3.50; Omissions in documentation for crash reporting
Date: Thu, 21 Feb 2013 11:27:06 +0400	[thread overview]
Message-ID: <87bobei0tx.fsf@yandex.ru> (raw)

As a non-GDB-wielding user with not much C experience, I had a hard time
following the instructions in `report-emacs-bug' and the ones that
followed.

1. Calling `xbacktrace' requires src/.gdbinit to be loaded. It
a) requires the user to run gdb exactly from src/ (not `gdb src/emacs'),
b) requires them to modify the `auto-load safe-path', or that .gdbinit
is ignored.

2. "Compile without optimizations" - how do I do that? `configure
--help' doesn't seem to show any pertinent options. ...but wait, it says
I can override the choices made by the script.
a) Do I set the variable when calling `make', or do I have to re-run
./configure? Not obvious, the answer is "the latter".
b) I don't know the choice the script made, how do I not break
anything by overriding it? My first choice was "-O0", and that resulted
in an unoptimized build with no debugging symbols (I think).

3. In #13749 (which caused me to write this), Paul also suggests using
-DENABLE_CHECKING. If I'm not mistaken, this variable isn't documented
anywhere.





             reply	other threads:[~2013-02-21  7:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21  7:27 Dmitry Gutov [this message]
2013-02-21  8:31 ` bug#13775: 24.3.50; Omissions in documentation for crash reporting Andreas Schwab
2013-02-21 17:24 ` Eli Zaretskii
2013-02-22  1:31   ` Dmitry Gutov
2013-02-22  9:24     ` Eli Zaretskii
2013-02-22 21:53       ` Dmitry Gutov
2013-02-22  9:37     ` Andreas Schwab
2013-02-22 21:26       ` Dmitry Gutov
2013-02-22 21:44         ` Eli Zaretskii
2013-02-22 22:00           ` Dmitry Gutov

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=87bobei0tx.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=13775@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.