From: Eli Zaretskii <eliz@gnu.org>
To: Itai Berli <itai.berli@gmail.com>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Help getting started debugging Emacs on macOS Sierra
Date: Fri, 11 Aug 2017 12:35:14 +0300 [thread overview]
Message-ID: <83wp6aqwfh.fsf@gnu.org> (raw)
In-Reply-To: <CABsNJ=POaKaUTkP=0H=UYQT+RtzC_HhWArtXQ=64sVV1_neH8Q@mail.gmail.com> (message from Itai Berli on Fri, 11 Aug 2017 11:57:10 +0300)
> From: Itai Berli <itai.berli@gmail.com>
> Date: Fri, 11 Aug 2017 11:57:10 +0300
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> OK. So I've installed gdb, and rebuilt Emacs as Eli suggested. I have then imported the project to Eclipse IDE
> for C/C++ Developers (Oxygen Release 4.7.0). I have no trouble running the GUI from Eclipse. However,
> when when I try to debug it, I get the following error message:
>
> ---
> 'Launching emacs-26.0.50.1' has encountered a problem.
> Error in final launch sequence
> Failed to execute MI command:
> -exec-run
> Error message from debugger back end:
> During startup program terminated with signal ?, Unknown signal.
> During startup program terminated with signal ?, Unknown signal.
I don't use Eclipse, so I'm stabbing in the dark here. The error
message means that there's some problem between Eclipse and the
underlying debugger with respect to GDB/MI commands emitted by
Eclipse. Google finds several discussions for these error messages,
so maybe you will b e able to find a solution there.
An alternative is to use the Emacs's front-end for GDB, it is started
with "M-x gdb RET".
next prev parent reply other threads:[~2017-08-11 9:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:25 Help getting started debugging Emacs on macOS Sierra Itai Berli
2017-08-11 3:04 ` Paul Eggert
2017-08-11 5:06 ` Itai Berli
2017-08-11 8:47 ` Paul Eggert
2017-08-11 8:57 ` Itai Berli
2017-08-11 9:27 ` Itai Berli
2017-08-11 9:52 ` Eli Zaretskii
2017-08-11 9:55 ` Itai Berli
2017-08-11 9:59 ` Itai Berli
2017-08-11 10:09 ` Itai Berli
2017-08-11 11:46 ` Tino Calancha
2017-08-11 12:14 ` Itai Berli
2017-08-11 12:33 ` Tino Calancha
2017-08-11 12:40 ` Itai Berli
2017-08-11 12:48 ` Tino Calancha
2017-08-11 13:17 ` Itai Berli
2017-08-11 13:20 ` Tino Calancha
2017-08-11 13:25 ` Itai Berli
2017-08-11 14:18 ` Eli Zaretskii
2017-08-11 14:42 ` Itai Berli
2017-08-11 15:08 ` Eli Zaretskii
2017-08-11 15:34 ` Itai Berli
2017-08-11 16:07 ` Itai Berli
2017-08-11 16:08 ` Eli Zaretskii
2017-08-11 17:32 ` Itai Berli
2017-08-12 9:53 ` Itai Berli
2017-08-12 10:20 ` Eli Zaretskii
2017-08-12 10:43 ` Itai Berli
2017-08-12 11:43 ` Tino Calancha
2017-08-12 11:59 ` Stephen Berman
2017-08-12 12:08 ` Itai Berli
2017-08-12 12:14 ` Stephen Berman
2017-08-12 12:15 ` Eli Zaretskii
2017-08-12 13:28 ` Itai Berli
2017-08-12 13:47 ` Tino Calancha
2017-08-12 14:20 ` Anders Lindgren
2017-08-12 11:57 ` Eli Zaretskii
2017-08-11 12:43 ` Eli Zaretskii
2017-08-11 9:35 ` Eli Zaretskii [this message]
2017-08-11 6:28 ` Eli Zaretskii
2017-08-11 8:27 ` Itai Berli
2017-08-11 9:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wp6aqwfh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=itai.berli@gmail.com \
/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.