unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: git+master: c6e6503900534d939dd94b812563c27f22c49b7d crash when using gnus
Date: Sat, 28 Apr 2018 15:09:10 +0300	[thread overview]
Message-ID: <83a7tnttw9.fsf@gnu.org> (raw)
In-Reply-To: <874ljvh7df.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 28 Apr 2018 13:56:28 +0200)

> From: Uwe Brauer <oub@mat.ucm.es>
> Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
> Date: Sat, 28 Apr 2018 13:56:28 +0200
> 
>    > Basically, start GDB with Emacs as the executable to debug, then run
>    > Emacs from GDB's command line.
> 
> 
> Oh well,
> 
> I tried gdb /opt/emacs27/bin/emacs
> and I obtained
> Reading symbols from /opt/emacs27/bin/emacs...(no debugging symbols
> found)...done.

Your Emacs was not built with debugging symbols.  The "Preliminaries"
section of etc/DEBUG explains how to build with debugging symbols.

> But no emacs started.

Because you didn't start it.  The GDB "run" command starts the
executable.  This is again described in etc/DEBUG.

> The message indicates that I should recompile emacs?

Yes.

>    > No need to google, the answer is under your fingertips: see the
>    > beginning of the file etc/DEBUG in the Emacs source tree.
> 
> Thanks, but just read it, but it is a bit confusing, since it is not
> clear to me whether I could start emacs first and then start gdb within
> emacs.

You can either start GDB from (another session of) Emacs, or start GDB
from the shell prompt.  In both cases, you should then start Emacs
from GDB.

> So shall I recompile emacs with debug options like
> 
>   CFLAGS='-O0 -g3' ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type

Yes, that's a good beginning.



  reply	other threads:[~2018-04-28 12:09 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 [this message]
2018-04-29  8:46           ` Uwe Brauer
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=83a7tnttw9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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).