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: Mon, 28 Feb 2022 11:30:51 -0300 [thread overview]
Message-ID: <87bkyr5a7s.fsf@gmail.com> (raw)
In-Reply-To: <83pmn7m8px.fsf@gnu.org>
On Mon, 28 Feb 2022 at 15:17, Eli Zaretskii <eliz@gnu.org> wrote:
> This means your system disables the system call that allows GDB to
> attach to a running process. Can you change the setting the error
> message mentions above, or ask your sysadmins to change it for you, or
> do something else to grant you the privilege of attaching a debugger
> to a process? If you can do that, please try this method again after
> enabling that privilege.
It's a personal computer, so I'm the "sysadmin". It was a setting done
by the distro, and I changed it. Then I tried the following.
Started `./emacsclient -c -a=""' and then `M-x gdb RET gdb -i=mi -p
<emacs pid> RET'. Where the PID was the same and only instance of Emacs
I had opened. This resulted in GDB getting stuck at "initializing...".
I presume "attaching to itself" is not the thing.
So I started two Emacs instances, one `./emacsclient -c -a=""' from
`lib-src/', and another standalone instance. So I starded GDB from the
standalone instance using the PID from the daemon with `M-x gdb RET gdb
-i=mi -p <emacs daemon pid> RET'. This gets me almost there I think,
but not quite. It appears to attach successfully:
#+begin_example
Attaching to process 10785
[New LWP 10786]
[New LWP 10787]
[New LWP 10788]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fa139664246 in __pselect (nfds=21, readfds=0x7fff480be100,
writefds=0x7fff480be180, exceptfds=0x0, timeout=<optimized out>,
sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/pselect.c:48
48 ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
#+end_example
However, I also get a message that "Target doesn’t support non-stop
mode. Turning it off." And indeed, the other instance to which I
attached GDB becomes completely unresponsive until I quit GDB, so I
cannot trigger the problem, since I cannot interact with it.
next prev parent reply other threads:[~2022-02-28 14:30 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 [this message]
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
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
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=87bkyr5a7s.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 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).