From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54183@debbugs.gnu.org
Subject: bug#54183: 28.0.91; Emacs crashes on bookmark-jump
Date: Thu, 03 Mar 2022 11:23:04 -0300 [thread overview]
Message-ID: <87lexryubo.fsf@gmail.com> (raw)
In-Reply-To: <838rtrjf7l.fsf@gnu.org>
On Thu, 03 Mar 2022 at 16:14, Eli Zaretskii <eliz@gnu.org> wrote:
>
> I suspect that the way you started Emacs actually ran the installed
> executable of Emacs, without the patch. Can you verify which
> executable file is being run? One way to be sure is to try this
> command after you attach to a running Emacs:
>
> (gdb) break gui_define_fringe_bitmap
>
> If this says the function gui_define_fringe_bitmap is not defined, you
> are running the old unpatched executable.
>
Your suspicion is right. From the same session I've reported the last
crash:
(gdb) break gui_define_fringe_bitmap
Function "gui_define_fringe_bitmap" not defined.
Breakpoint 1 (gui_define_fringe_bitmap) pending.
However, I did follow carefully the instructions. The patch reported to
have been applied to each of the affected files. And, since I was
unfamiliar with the procedure, before running `make', I rechecked each
of the patched files to see if they contained the changed, and they did.
As far as I understand, this means that when I call
`lib-src/emacsclient' it was actually bringing the installed `emacs' all
along. Luckily, for the previous tests, it just so happened that it was
identical to the version we wanted to test. But this is no longer the
case now, given the patch. Is this correct?
And that's the procedure I had been following given the problem does not
occur on a standalone Emacs instance.
That given, does starting it with `src/emacs --daemon', then connecting
with `lib-src/emacsclient' seem like the correct procedure to you?
next prev parent reply other threads:[~2022-03-03 14:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 14:57 bug#54183: 28.0.91; Emacs crashes on bookmark-jump Gustavo Barros
2022-02-27 16:33 ` Eli Zaretskii
2022-02-27 20:33 ` Gustavo Barros
2022-02-28 3:24 ` Eli Zaretskii
2022-02-28 11:01 ` Gustavo Barros
2022-02-28 13:17 ` Eli Zaretskii
2022-02-28 14:30 ` Gustavo Barros
2022-02-28 14:54 ` Eli Zaretskii
2022-02-28 15:47 ` Gustavo Barros
2022-02-28 17:14 ` Eli Zaretskii
2022-02-28 18:00 ` Eli Zaretskii
2022-02-28 18:33 ` Gustavo Barros
2022-03-01 14:43 ` Eli Zaretskii
2022-03-01 18:04 ` Gustavo Barros
2022-03-01 18:41 ` Gustavo Barros
2022-03-02 3:23 ` Eli Zaretskii
2022-03-02 10:52 ` Gustavo Barros
2022-03-02 11:11 ` Eli Zaretskii
2022-03-02 11:15 ` Gustavo Barros
2022-03-03 9:41 ` Eli Zaretskii
2022-03-03 13:13 ` Gustavo Barros
2022-03-03 14:14 ` Eli Zaretskii
2022-03-03 14:23 ` Gustavo Barros [this message]
2022-03-03 14:57 ` Gustavo Barros
2022-03-03 15:23 ` Gustavo Barros
2022-03-03 16:43 ` Eli Zaretskii
2022-03-03 18:10 ` Gustavo Barros
2022-03-03 18:33 ` Eli Zaretskii
2022-03-03 18:41 ` Gustavo Barros
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=87lexryubo.fsf@gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=54183@debbugs.gnu.org \
--cc=eliz@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.