From: Eli Zaretskii <eliz@gnu.org>
To: Kun Liu <kun.liu@gmail.com>
Cc: 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sat, 04 May 2024 10:11:03 +0300 [thread overview]
Message-ID: <86wmoagigo.fsf@gnu.org> (raw)
In-Reply-To: <CA+Nei8ND2BMuUkNa=o8Lfv88SOudme5JKwZEM5mw95j31wUjew@mail.gmail.com> (message from Kun Liu on Fri, 3 May 2024 14:30:37 -0700)
> From: Kun Liu <kun.liu@gmail.com>
> Date: Fri, 3 May 2024 14:30:37 -0700
>
> Emacs is running inside VirtualBox on Windows 11. It randomly crashes
> when I do a copy from other apps running on the host, e.g., Chrome on
> Windows 11.
Emacs seems to segfault trying to display an invalid Lisp object. The
invalid object seems to come from an error message. IOW, Emacs tried
to signal an error, and crashed showing the data of the error. I have
no idea how VirtualBox converts Windows clipboard data into X
clipboard/selection data -- do you happen to know? The reason of this
problem is probably there.
However, please provide more details, as the backtrace below doesn't
say enough.
First, please say "source src/.gdbinit" in GDB, to have special
commands in .gdbinit defined, which help in debugging Emacs.
Second, please rebuild Emacs with "-O0 -g3", so that debug info is
more comprehensive.
After that, when Emacs crashes, show the backtrace, which should now
include the Lisp backtrace as well (by virtue of src/.gdbinit).
And finally, the values of the following variables are of interest:
> #11 0x000055b069603f3e in print_error_message (data=<optimized out>, data@entry=0x55b085976613,
> stream=stream@entry=0x30, context=<optimized out>, caller=caller@entry=0x7fe0) at lisp.h:1172
> obj = <optimized out>
> li = {tortoise = 0x55b0859765f3, max = 2, n = 0, q = 1}
> sep = 0x55b0696ad6a0 ", "
> errname = 0x11f40
> errmsg = 0x55b06c78e6e4
> file_error = 0x0
> tail = 0x55b0859765e3
In this call-stack frame, what is the value of 'data'? It is a Lisp
object, so showing it should involve using the commands xtype, xcar,
and xcdr, and probably also xstring (which are defined in .gdbinit).
Also, if you know what was the text copied from the other application,
please show that text.
Thanks.
next prev parent reply other threads:[~2024-05-04 7:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 21:30 bug#70760: 29.3.50; core dumps when copy in other apps Kun Liu
2024-05-04 7:11 ` Eli Zaretskii [this message]
2024-05-04 18:08 ` Kun Liu
2024-05-04 19:02 ` Eli Zaretskii
[not found] ` <CA+Nei8PsdEL-bOOQg86aZk1n1ahpb38XUokyHR98muaRTUY+5Q@mail.gmail.com>
2024-05-04 21:37 ` Kun Liu
2024-05-05 5:11 ` Eli Zaretskii
2024-05-05 15:45 ` Kun Liu
2024-05-05 16:12 ` Eli Zaretskii
2024-05-05 16:44 ` Kun Liu
2024-05-05 17:11 ` Kun Liu
2024-05-05 17:34 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 6:17 ` Kun Liu
2024-05-14 7:13 ` Eli Zaretskii
2024-05-15 10:35 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 16:27 ` Kun Liu
2024-05-15 17:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 18:25 ` Kun Liu
2024-05-15 21:06 ` Kun Liu
2024-05-16 9:20 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 19:07 ` Kun Liu
2024-05-17 16:23 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 17:34 ` Eli Zaretskii
2024-05-17 20:43 ` Kun Liu
2024-05-18 0:34 ` Kun Liu
2024-05-18 10:32 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 11:44 ` Eli Zaretskii
2024-05-18 11:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 12:09 ` Eli Zaretskii
2024-05-18 16:55 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 17:54 ` Eli Zaretskii
2024-05-18 18:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 19:20 ` Eli Zaretskii
2024-05-16 9:07 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86wmoagigo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70760@debbugs.gnu.org \
--cc=kun.liu@gmail.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 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.