all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Toon Claes <toon@iotcl.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: perry@piermont.com, dancol@dancol.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: lldb support
Date: Thu, 10 Nov 2016 17:27:18 +0100	[thread overview]
Message-ID: <m2bmxn7121.fsf@MacToonPro-2.local> (raw)
In-Reply-To: <83fumzfhtv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Nov 2016 17:57:48 +0200")

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

> Instead, please invoke "M-x gdb RET".  It will suggest a command line
> that assumes GDB; please change it as lldb-mi requires.

Well, I also tried that. But gives the error:

    Error: you did not specify -i=mi on GDB's command line!

After that also a lot of other errors occur:

    5^error,msg="Driver. Received command '5-file-list-exec-source-files'. It was not handled. Command 'file-list-exec-source-files' not in Command Factory"
    6^error,msg="Driver. Received command '6-file-list-exec-source-file'. It was not handled. Command 'file-list-exec-source-file' not in Command Factory"
    8^error,msg="Command 'stack-info-frame'. Invalid process during debug session"
    10^error,msg="Driver. Received command '10-break-list'. It was not handled. Command 'break-list' not in Command Factory"
    12^error,msg="Driver. Received command '12-break-list'. It was not handled. Command 'break-list' not in Command Factory"

So results aren't very hopeful.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 841 bytes --]

  reply	other threads:[~2016-11-10 16:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 20:05 lldb support Perry E. Metzger
2016-11-07 20:20 ` Stefan Monnier
2016-11-08  3:08   ` Perry E. Metzger
2016-11-08 13:19     ` Stefan Monnier
2016-11-08 19:58       ` John Wiegley
2016-11-09  0:54     ` Richard Stallman
2016-11-09  1:17       ` Daniel Colascione
2016-11-09  3:42         ` Eli Zaretskii
2016-11-10  0:24         ` Richard Stallman
2016-11-10  0:26           ` Daniel Colascione
2016-11-11  1:26             ` Richard Stallman
2016-11-11  4:24               ` Stefan Monnier
2016-11-11  4:46               ` Nikolaus Rath
2016-11-12  0:42                 ` Richard Stallman
2016-11-11  9:44               ` Philippe Vaucher
2016-11-11 17:11                 ` Stefan Monnier
2016-11-11 17:42                 ` Stefan Huchler
2016-11-11 17:47                 ` John Wiegley
2016-11-12  0:59                   ` Stefan Huchler
2016-11-12 22:30                   ` Richard Stallman
2016-11-14 21:58                     ` John Wiegley
2016-11-16  4:13                       ` Joseph Mingrone
2016-11-16 14:27                         ` Stefan Monnier
2016-12-25 20:43                       ` Richard Stallman
2016-11-11 19:01               ` Sam Steingold
2016-11-12  1:02                 ` Stefan Huchler
2016-11-12 22:25                 ` Richard Stallman
2016-11-12  0:54               ` Perry E. Metzger
2016-11-12 22:30                 ` Richard Stallman
2016-11-10  1:51           ` Perry E. Metzger
2016-11-10  1:57           ` Perry E. Metzger
2016-11-10  3:43             ` Eli Zaretskii
2016-11-10  9:33               ` Toon Claes
2016-11-10 15:57                 ` Eli Zaretskii
2016-11-10 16:27                   ` Toon Claes [this message]
2016-11-10 17:19                     ` Eli Zaretskii
2016-11-12  7:04                       ` Toon Claes
2016-11-12  7:47                         ` Eli Zaretskii
2017-01-04 21:35                       ` Toon Claes
2016-11-10 13:58               ` Perry E. Metzger
2016-11-10 16:02                 ` Eli Zaretskii
2016-11-09  1:37       ` John Wiegley
2016-11-09  3:06       ` Perry E. Metzger
2016-11-10  0:23         ` Richard Stallman
2016-11-10  1:18           ` John Mastro

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=m2bmxn7121.fsf@MacToonPro-2.local \
    --to=toon@iotcl.com \
    --cc=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=perry@piermont.com \
    --cc=rms@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.