From: aprekates <aprekates@posteo.net>
To: tomas@tuxteam.de, help-gnu-emacs@gnu.org
Subject: Re: Trying to debug assemly
Date: Thu, 19 Dec 2019 03:18:29 +0200 [thread overview]
Message-ID: <974f1a63-1b71-5ed6-1b77-b576b4ec50cd@posteo.net> (raw)
In-Reply-To: <21755878-a78d-04e6-e169-20be43a38d45@posteo.net>
|||I've learned about three ways to initiate a debugging session in
emacs with gdb.|
||a. M-x gud-gdb||
|||b. M-x gdb|
|c. M-x gdb --interpreter=mi
|
|Does option a. uses GDB/MI interface?|
|Alexandros.
|
||
||
On 19/12/19 2:38 π.μ., aprekates wrote:
> Thanks.
>
> So if i want to debug in emacs with gdb and have ide like
> functionality , giving me the ability to create breakpoint by clicking
> next to source lines or windows with updates on variables, registers ,
> memory region etc then gdb must be able ta accept 'machine' like
> commands from the emacs gdb frontent.
>
> Alexandros.
>
> GDB/MI
>
> On 18/12/19 10:39 π.μ., tomas@tuxteam.de wrote:
>> On Wed, Dec 18, 2019 at 04:30:38AM +0200, aprekates wrote:
>>> Thanks.
>>>
>>> That worked. Although i dont quite understand what is the /GDB/MI
>>> interface./
>> GDB/MI is the so-called "machine interface". Back Then (TM), GDB was
>> just an interactive program: you type in things, GDB displays things
>> to you. With time, more-or-less graphical front ends appeared (among
>> them, of course, something written in Emacs). It became clear that
>> the interactive user interface wasn't the ideal way for a program to
>> control GDB, and thus MI was born.
>>
>> Cheers
>> -- t
>
next prev parent reply other threads:[~2019-12-19 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 1:22 Trying to debug assemly aprekates
2019-12-17 7:27 ` Andrew Savonichev
2019-12-18 2:30 ` aprekates
2019-12-18 8:39 ` tomas
2019-12-19 0:38 ` aprekates
2019-12-19 1:18 ` aprekates [this message]
2019-12-17 9:08 ` VanL
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=974f1a63-1b71-5ed6-1b77-b576b4ec50cd@posteo.net \
--to=aprekates@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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.