unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eason Huang <aqua0210@foxmail.com>
Cc: 60556@debbugs.gnu.org
Subject: bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10
Date: Sun, 22 Jan 2023 13:55:07 +0200	[thread overview]
Message-ID: <83sfg2kcmc.fsf@gnu.org> (raw)
In-Reply-To: <tencent_4738FA5AC1A698DCFD0B48891C92C1061906@qq.com> (message from Eason Huang on Sun, 22 Jan 2023 19:22:23 +0800)

> From: Eason Huang <aqua0210@foxmail.com>
> Cc: 60556@debbugs.gnu.org
> Date: Sun, 22 Jan 2023 19:22:23 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > At this point, instead of "q", please type:
> >
> >   (gdb) thread 1
> >   (gdb) bt
> >
> > and post the results here.
> >
> >
> >
> >
> 
> Hi Eli,
> 
> I tried to debug with GDB again and reproduce the issue and the result
> is as bellow:

Thanks.  I guess I shouldn't make any assumptions.  So, one last time:
please reproduce the issue, and type:

  (gdb) thread apply all bt

This should produce a backtrace from all the threads in the Emacs
process.  I'd like to see where did we call the abort function, the
one which pops up the Abort dialog.





  reply	other threads:[~2023-01-22 11:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 14:44 bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10 Eason Huang
2023-01-22  4:30 ` Eason Huang
2023-01-22  6:34   ` Eason Huang
2023-01-23 18:26   ` João Távora
2023-01-23 19:00     ` Eli Zaretskii
2023-01-24 12:50     ` Eason Huang
2023-01-22 11:03 ` Eli Zaretskii
2023-01-22 11:22   ` Eason Huang
2023-01-22 11:55     ` Eli Zaretskii [this message]
2023-01-22 12:11       ` Eason Huang
2023-01-22 13:05         ` Eli Zaretskii
2023-01-22 13:27           ` Eason Huang
2023-01-22 14:03             ` Eli Zaretskii
2023-01-22 14:39               ` Eason Huang
2023-01-22 14:40                 ` 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=83sfg2kcmc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60556@debbugs.gnu.org \
    --cc=aqua0210@foxmail.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).