From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 66068@debbugs.gnu.org
Subject: bug#66068: 30.0.50; xwidget-webkit-browse-url makes Emacs abort
Date: Sun, 24 Sep 2023 17:12:49 +0200 [thread overview]
Message-ID: <87fs338v0u.fsf@gmx.net> (raw)
In-Reply-To: <87msxhtto4.fsf@yahoo.com> (Po Lu's message of "Wed, 20 Sep 2023 11:22:51 +0800")
On Wed, 20 Sep 2023 11:22:51 +0800 Po Lu <luangruo@yahoo.com> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> On Mon, 18 Sep 2023 22:11:31 +0800 Po Lu <luangruo@yahoo.com> wrote:
>>
>>> Stephen Berman <stephen.berman@gmx.net>
>>>
>>>> (gdb) up 0
>>>> #0 x_error_quitter (display=0x555555ead980, event=0x7fffffffc950)
>>>> at /home/steve/src/emacs/emacs-master/src/xterm.c:26905
>>>> 26905 {
>>>> (gdb) p *error
>>>> $1 = {void (const char *, ...)} 0x55555575ae68 <error>
>>>>
>>>> FWIW, I get the same output when I run Emacs in gdb with -xrm
>>>> "emacs.synchronous: true", as requested by Eli.
>>>
>>> My apologies, I intended to ask for:
>>>
>>> (gdb) p *event
>>
>> No problem:
>>
>> (gdb) r -Q -xrm "emacs.synchronous: true"
>> [...]
>> (gdb) frame 0
>> #0 x_error_quitter (display=0x555555ead980, event=0x7fffffffc930)
>> at /home/steve/src/emacs/emacs-master/src/xterm.c:26905
>> 26905 {
>> (gdb) p *event
>> $1 = {
>> type = 0,
>> display = 0x555555ead980,
>> resourceid = 62914833,
>> serial = 3527,
>> error_code = 168 '\250',
>> request_code = 151 '\227',
>> minor_code = 32 ' '
>> }
>
> Would you please send the backtrace from this as well? The request code
> does not match that of any core request or extension on your display,
> and the backtrace you previously enclosed was not produced from an Emacs
> running synchronously.
(Sorry for not responding sooner; I was travelling.) I already posted a
backtrace produced from -Q -xrm "emacs.synchronous: true" in the message
I referred to above, see the attachment to <87a5tjd6bd.fsf@gmx.net>
<https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-09/msg01928.html>.
Though as I pointed out in that message, the only apparent differences
from the first backtrace (produced from just -Q) are the specific
numerical values of addresses, struct members, etc. Just to be sure I
just now repeated the asynchronous run again and got again a
structurally identical backtrace (i.e., differing only in address and
struct member numerical values).
Steve Berman
next prev parent reply other threads:[~2023-09-24 15:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 10:06 bug#66068: 30.0.50; xwidget-webkit-browse-url makes Emacs abort Stephen Berman
2023-09-18 11:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 12:16 ` Stephen Berman
2023-09-18 14:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 15:08 ` Stephen Berman
2023-09-20 3:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 15:12 ` Stephen Berman [this message]
2023-09-25 0:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 8:47 ` Stephen Berman
2023-09-25 9:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 10:22 ` Stephen Berman
2023-09-30 10:03 ` Stephen Berman
2023-09-30 11:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 12:09 ` Stephen Berman
2023-09-18 11:28 ` Eli Zaretskii
2023-09-18 12:17 ` Stephen Berman
2023-12-07 10:28 ` Ramon Diaz-Uriarte
2023-12-09 15:12 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 20:39 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-10 5:32 ` Eli Zaretskii
2023-12-10 13:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-10 15:02 ` Eli Zaretskii
2023-12-10 15:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-10 15:47 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11 0:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11 9:55 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11 10:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-10 15:49 ` Eli Zaretskii
2023-12-11 21:03 ` Ramon Diaz-Uriarte
2024-09-04 11:23 ` Peter Oliver
2024-09-05 8:14 ` Eli Zaretskii
2024-09-07 9:32 ` Eli Zaretskii
2024-09-14 7:45 ` Eli Zaretskii
2024-09-14 12:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 14:21 ` Stefan Kangas
2024-09-21 9:01 ` Eli Zaretskii
2024-09-21 21:45 ` bug#66068: removing the WebKit when webkit2gtk3-2.42.5-1.el9.x86_64 will not alllow RL9 to configure Doug Maxey
2024-09-22 5:05 ` Eli Zaretskii
[not found] ` <db88e0b43b02580ee78171c3b0d55bcda6b2a458.camel@maxeygroup.tech>
2024-09-23 11:14 ` 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=87fs338v0u.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=66068@debbugs.gnu.org \
--cc=luangruo@yahoo.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).