all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Itai Berli <itai.berli@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Help getting started debugging Emacs on macOS Sierra
Date: Sat, 12 Aug 2017 12:53:24 +0300	[thread overview]
Message-ID: <CABsNJ=PwGYt7qci7KtfUfAcSzP2mufOB-Vjj-A4AM5Oz3kbrFQ@mail.gmail.com> (raw)
In-Reply-To: <CABsNJ=MADkWM1KraFBSs0sbJrRZQazvH2oYSWcQZRqnKfVQvSw@mail.gmail.com>

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

If I make a change to the code, for experimentation purposes, how do I
compile it so I can see my change in action and debug it? Should I run

./autogen.sh
./autogen.sh git
CFLAGS='-O0 -g3' ./configure
make
make install

or can I simply compile the file that I changed with the compiler (GCC or
Clang)?

On Fri, Aug 11, 2017 at 8:32 PM, Itai Berli <itai.berli@gmail.com> wrote:

> Thank you, Eli.
>
> On Fri, Aug 11, 2017 at 7:08 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > From: Itai Berli <itai.berli@gmail.com>
>> > Date: Fri, 11 Aug 2017 18:34:08 +0300
>> > Cc: Emacs developers <emacs-devel@gnu.org>
>> >
>> > > Tell me what you want to do and with what text, and then I might be
>> able to help you do
>> > that in a more useful way.
>> >
>> > I just want to get more familiar with the bidi algorithm and the way it
>> is implemented by Emacs. I'd like to try
>> > various small phrases, such as the ones that can be found in this
>> article:
>> > https://www.w3.org/International/articles/inline-bidi-markup/uba-basics
>>
>> After entering GDB, set a breakpoint in a function called
>> Fredraw_display, then run Emacs ("run -Q").  Insert the text you want,
>> then move point to its beginning and type "C-x =".  Remember the
>> buffer position displayed as result, let's call it POS.
>>
>> Then type "M-x redraw-display RET".  GDB will get control, and you can
>> now put breakpoints where you want.  For tracing through the bidi.c
>> code, I'd suggest this:
>>
>>   (gdb) break bidi_get_next_char_visually if bidi_it->charpos == POS
>>   (gdb) continue
>>
>> When the breakpoint in bidi_get_next_char_visually breaks, you can
>> step through the code using the "step" and "next" commands (you have
>> tool-bar buttons for them).
>>
>> Note that bidi_get_next_char_visually is called for each character the
>> display engine wants to display, so when it returns, it puts in
>> bidi_it->charpos the position of the next character in visual order.
>>
>
>

[-- Attachment #2: Type: text/html, Size: 3227 bytes --]

  reply	other threads:[~2017-08-12  9:53 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 [this message]
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
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='CABsNJ=PwGYt7qci7KtfUfAcSzP2mufOB-Vjj-A4AM5Oz3kbrFQ@mail.gmail.com' \
    --to=itai.berli@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.