From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Dmitrii Kuragin <kuragin@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 57434@debbugs.gnu.org
Subject: bug#57434: 28.1.91; Terminal Emacs Mac OS flickering.
Date: Mon, 29 Aug 2022 17:15:41 +0200 [thread overview]
Message-ID: <m2zgfn5bdu.fsf@Mini.fritz.box> (raw)
In-Reply-To: <CALqSXk6-4kYHyTqPNgpBQNPsUx5tETOZH05Ty_jC5fw34AADVQ@mail.gmail.com> (Dmitrii Kuragin's message of "Mon, 29 Aug 2022 07:18:43 -0700")
Dmitrii Kuragin <kuragin@google.com> writes:
> I am having difficulty running a debugger.
>
> I tried gdb and signing, but it didn't work. I also tried lldb, but it doesn't stop on a breakpoint for whatever reason.
>
> I compiled with `-O0 -g3`, then
> ```
> lldb
> (lldb) file nextstep/Emacs.app/Contents/MacOS/Emacs
> Current executable set to '/Users/kuragin/Desktop/emacs/nextstep/Emacs.app/Contents/MacOS/Emacs' (x86_64).
> (lldb) breakpoint set -f scroll.c -l 270
> Breakpoint 1: where = Emacs`do_scrolling + 485 at scroll.c:271:11, address = 0x0000000100032da5
> ```
>
> But, it doesn't stop there...
>
> and I run Emacs like this:
> ```
> arch --x86_64 make configure="CFLAGS='-O0 -g3'" -j 20 && nextstep/Emacs.app/Contents/MacOS/Emacs -nw
I'm afraid I can't help here. because GDB doesn't support my platform.
There is something about using GDB with TTY Emacs in etc/DEBUG though.
Maybe that helps.
LLDB doesn't work for me, neither the one from Apple, nor from LLVM 14.
For some reason, SIGTTOU seems to be behave differently when running
Emacs -nw under LLDB, even when I tell LLDB to not stop or report it.
Or so I think, I'm not an LLDB expert.
Here is what I tried
cd src
lldb emacs
b main
run -Q -nw
process handle -s false -n false SIGTTOU
c
but then Emacs gets stuck. Maybe it's a bug in LLDB.
next prev parent reply other threads:[~2022-08-29 15:15 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:54 bug#57434: 28.1.91; Terminal Emacs Mac OS flickering Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-27 5:34 ` Gerd Möllmann
2022-08-27 5:41 ` Gerd Möllmann
2022-08-27 15:03 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-27 15:46 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-27 15:58 ` Eli Zaretskii
2022-08-27 16:01 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-27 16:14 ` Eli Zaretskii
2022-08-29 14:18 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 14:38 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 16:04 ` Eli Zaretskii
2022-08-29 16:05 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 16:07 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 16:27 ` Eli Zaretskii
2022-08-29 15:15 ` Gerd Möllmann [this message]
2022-08-29 16:22 ` Eli Zaretskii
2022-08-29 17:14 ` Gerd Möllmann
2022-08-29 18:24 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 18:57 ` Eli Zaretskii
2022-08-29 19:04 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 19:17 ` Eli Zaretskii
2022-08-29 19:26 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 19:37 ` Eli Zaretskii
2022-08-29 20:25 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 20:44 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 21:08 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 11:28 ` Eli Zaretskii
2022-08-30 6:09 ` Gerd Möllmann
2022-08-30 11:10 ` Eli Zaretskii
2022-08-30 11:23 ` Gerd Möllmann
2022-08-30 13:48 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 16:19 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 16:34 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 17:00 ` Eli Zaretskii
2022-08-30 17:22 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 11:11 ` Eli Zaretskii
2022-08-30 6:04 ` Gerd Möllmann
2022-08-30 11:46 ` Eli Zaretskii
2022-08-30 11:53 ` Gerd Möllmann
2022-08-30 12:07 ` Eli Zaretskii
2022-08-30 12:15 ` Gerd Möllmann
2022-08-30 12:48 ` Eli Zaretskii
2022-08-30 13:25 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 13:48 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 6:14 ` Gerd Möllmann
2022-08-31 6:14 ` Gerd Möllmann
2022-08-31 7:02 ` Gerd Möllmann
2022-08-31 11:09 ` Eli Zaretskii
2022-08-31 11:54 ` Gerd Möllmann
2022-08-31 14:12 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 14:38 ` Gerd Möllmann
2022-08-31 16:00 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 16:21 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 16:34 ` Eli Zaretskii
2022-08-31 17:11 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 16:25 ` Eli Zaretskii
2022-09-01 5:44 ` Gerd Möllmann
2022-09-01 6:11 ` Eli Zaretskii
2022-09-01 6:45 ` Gerd Möllmann
2022-09-01 8:18 ` Gerd Möllmann
2022-09-01 8:25 ` Eli Zaretskii
2022-09-01 8:56 ` Gerd Möllmann
2022-09-01 11:30 ` Eli Zaretskii
2022-09-01 12:27 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-01 12:32 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-01 12:36 ` Gerd Möllmann
2022-09-02 7:16 ` Eli Zaretskii
2022-09-02 7:26 ` Eli Zaretskii
2022-09-02 9:21 ` Gerd Möllmann
2022-09-03 8:04 ` Gerd Möllmann
2022-09-03 9:06 ` Eli Zaretskii
2022-09-03 16:35 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 16:51 ` Eli Zaretskii
2022-09-03 17:14 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 17:21 ` Eli Zaretskii
2022-09-04 4:55 ` Gerd Möllmann
2022-09-07 4:59 ` Gerd Möllmann
2022-09-07 16:11 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-07 18:17 ` Eli Zaretskii
2022-09-08 5:31 ` Gerd Möllmann
2022-09-08 6:25 ` Eli Zaretskii
2022-09-08 6:43 ` Gerd Möllmann
2022-09-08 8:20 ` Eli Zaretskii
2022-09-08 8:43 ` Gerd Möllmann
2022-09-08 9:16 ` Eli Zaretskii
2022-09-08 9:35 ` Gerd Möllmann
2022-09-08 15:59 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 15:48 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 16:00 ` Eli Zaretskii
2022-09-20 16:35 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-20 16:45 ` Eli Zaretskii
2022-09-21 6:10 ` Gerd Möllmann
2022-09-21 11:17 ` Eli Zaretskii
2022-09-02 9:20 ` Gerd Möllmann
2022-08-29 16:01 ` Eli Zaretskii
2022-08-29 16:03 ` Dmitrii Kuragin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 16:27 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zgfn5bdu.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57434@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kuragin@google.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).