From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: lldb support Date: Thu, 10 Nov 2016 19:19:20 +0200 Message-ID: <8337izfe1z.fsf@gnu.org> References: <20161107150552.20e98985@jabberwock.cb.piermont.com> <20161107220815.606cd583@jabberwock.cb.piermont.com> <6c239d49-a92c-1495-7121-4808295a4fc2@dancol.org> <20161109205724.02e086af@jabberwock.cb.piermont.com> <83h97gf19d.fsf@gnu.org> <83fumzfhtv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1478802279 15019 195.159.176.226 (10 Nov 2016 18:24:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 10 Nov 2016 18:24:39 +0000 (UTC) Cc: perry@piermont.com, dancol@dancol.org, rms@gnu.org, emacs-devel@gnu.org To: Toon Claes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 10 19:24:31 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c4u11-00080q-2i for ged-emacs-devel@m.gmane.org; Thu, 10 Nov 2016 19:23:59 +0100 Original-Received: from localhost ([::1]:48416 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4u14-00038M-2k for ged-emacs-devel@m.gmane.org; Thu, 10 Nov 2016 13:24:02 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4t0d-00018f-9S for emacs-devel@gnu.org; Thu, 10 Nov 2016 12:19:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4t0c-00083d-02 for emacs-devel@gnu.org; Thu, 10 Nov 2016 12:19:31 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4t0Y-0007vI-4k; Thu, 10 Nov 2016 12:19:26 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4851 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1c4t0Q-0006MM-OD; Thu, 10 Nov 2016 12:19:19 -0500 In-reply-to: (message from Toon Claes on Thu, 10 Nov 2016 17:27:18 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:209330 Archived-At: > From: Toon Claes > Cc: dancol@dancol.org, emacs-devel@gnu.org, rms@gnu.org, perry@piermont.com > Date: Thu, 10 Nov 2016 17:27:18 +0100 > > > 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! Doesn't lldb-mi accept the --interpreter=mi argument on its command line? That would be strange, since it's supposed to be a compatibility shim, and is advertised to work with Eclipse. If you disable this test in gdb-mi.el, do you get better results? > 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. These could be the result of not activating the MI mode in lldb-mi, because of the previous error message. How about asking the lldb-mi maintainers what should be the correct invocation of this tool? Thanks.