GNU bug report logs - #55047
Bug: Abort Dialog upon start

Previous Next

Package: emacs;

Reported by: hermit sings <hermitsings <at> yahoo.com>

Date: Thu, 21 Apr 2022 00:08:02 UTC

Severity: normal

Tags: moreinfo, unreproducible

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55047 in the body.
You can then email your comments to 55047 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Thu, 21 Apr 2022 00:08:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to hermit sings <hermitsings <at> yahoo.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Thu, 21 Apr 2022 00:08:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: Bug: Abort Dialog upon start
Date: Wed, 20 Apr 2022 22:56:58 +0000 (UTC)
[Message part 1 (text/plain, inline)]
Hi,
I have installed Emacs 28 newly on my Windows machine and I'm getting this dialog after starting Emacs and pressing a few commands (C-n). Previously, I had tried Emacs 27 and it did not have this problem. But this version surely has been giving me this dialog. I have uninstalled and reinstalled Emacs and tried whatever I could but I cannot solve it. A screenshot of the dialog is attached here.

Kindly help me with this.
Thanks and regards.




[Message part 2 (text/html, inline)]
[1650495096582blob.jpg (image/png, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Thu, 21 Apr 2022 05:46:01 GMT) Full text and rfc822 format available.

Message #8 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Thu, 21 Apr 2022 08:45:11 +0300
> Date: Wed, 20 Apr 2022 22:56:58 +0000 (UTC)
> From:  hermit sings via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> I have installed Emacs 28 newly on my Windows machine and I'm getting this dialog after starting Emacs
> and pressing a few commands (C-n). Previously, I had tried Emacs 27 and it did not have this problem. But
> this version surely has been giving me this dialog. I have uninstalled and reinstalled Emacs and tried
> whatever I could but I cannot solve it. A screenshot of the dialog is attached here.
> 
> Kindly help me with this.

Please install GDB for Windows, run Emacs under GDB, like this:

  C:\> gdb <PATH-TO-EMACS>\emacs.exe

then, when the abort dialog pops up, click "Yes".  GDB will show its
prompt "(gdb)".  Type "thread apply all bt", and post here everything
that prints.




Added tag(s) moreinfo. Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Thu, 21 Apr 2022 11:51:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Thu, 28 Apr 2022 10:38:01 GMT) Full text and rfc822 format available.

Message #13 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Thu, 28 Apr 2022 13:36:52 +0300
[Message part 1 (text/plain, inline)]
[Please use Reply All to reply, so that the bug tracker records this
discussion.]

> Date: Thu, 28 Apr 2022 10:08:35 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> 
> I am extremely sorry for the late response. Partly it was because your mail somehow was in my spam, I
> have no idea why. And secondly, because I could not run gdb. I am on Windows and tried to install and use
> gdb. Mingw only provides x86 gdb and it's not debugging emacs which is x64. So I downloaded from various
> sources but still could not work it out.
> 
> Finally, I downloaded an application: x64dbg and tried to debug Emacs 28.1 (C:\Program
> Files\Emacs\emacs-28.1\bin\emacs.exe).
> The log file which I could obtain using this software is attached with this mail.

Thanks, but this log doesn't help to explain the problem.

Please install the 64-bit GDB for Windows from the MSYS2 project:

  https://packages.msys2.org/package/mingw-w64-x86_64-gdb

[log.txt (text/plain, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 11:07:02 GMT) Full text and rfc822 format available.

Message #16 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>, Corwin Brust <corwin <at> bru.st>
Cc: 55047 <at> debbugs.gnu.org
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 14:06:15 +0300
[Please use Reply All.  Please do NOT reply only to me.]

> Date: Sat, 30 Apr 2022 10:56:20 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> 
> I have been trying to debug with MSYS GDB with the link you provided but even after 2 days and hours into
> it, I could not obtain a log. GDB shows `No debugging symbols found in ./emacs.exe` everytime. I've tried to
> search the web a lot for this but I could not make it to debug. I have also tried using `-g` but it shows this
> argument is unrecognized. I am attaching a screenshot of it with this mail.

Sorry about that, and thank you for your efforts.

It looks like the Emacs binary you use was stripped of the debugging
symbols, so it doesn't support any useful debugging.

There's a pretest version that should include debug symbols, here:

  https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/emacs-28.0.92.zip

Corwin, does the pretest include debug symbols in the Emacs binary, or
was that also stripped?

If Corwin replies that debug symbols are included, could you please
install that pretest version and try running it under GDB?  TIA.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 13:57:01 GMT) Full text and rfc822 format available.

Message #19 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 16:56:34 +0300
> Date: Sat, 30 Apr 2022 13:40:18 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> I tried to run it under GDB and it's giving the same message: 'No debugging
> symbols'.

Too bad.

Corwin, is there any binary of Emacs 28 anywhere that has debug
symbols, and that could be therefore used to debug this abort?

> However, this time after launching Emacs 28.0.92, it produced a
> backtrace file which Emacs 28.1 (which was installed in my system) didn't,
> although the dialog showed it would produce it in the working directory. I
> don't know if it's of any help but I will just provide that file here.

Thanks, but the backtrace file is not usable without debugging symbols
in the binary, either.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 14:01:01 GMT) Full text and rfc822 format available.

Message #22 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 16:59:58 +0300
> Date: Sat, 30 Apr 2022 13:40:18 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> I tried to run it under GDB and it's giving the same message: 'No debugging
> symbols'. However, this time after launching Emacs 28.0.92, it produced a
> backtrace file which Emacs 28.1 (which was installed in my system) didn't,
> although the dialog showed it would produce it in the working directory. I
> don't know if it's of any help but I will just provide that file here.

There should be an event logged in the Windows Event log, under
Applications, which reports some information about this abort.  Can
you look there and tell what it says?  The Event log should be
accessible by right-clicking on "Computer" and selecting "Manage".
Maybe it will tell us something helpful.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 16:17:02 GMT) Full text and rfc822 format available.

Message #25 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 19:16:23 +0300
> Date: Sat, 30 Apr 2022 15:46:35 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
> 	"55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, I tried using Windows Event Log. There are two errors registered after the Emacs fault event happens:
> 1. Application error and 2. Windows error. For both of the cases, there are two logs generated: 1. General
> and 2. Details.
> I'm providing both as files here. For general, I am providing .txt files, one for Emacs error and one for
> Windows error.
> And for detailed logs, I am providing XML files, one for Emacs and one for Windows error.
> Also, screenshots are here for additional data that was shown in the Event Log.

Thanks.  Exception 0x40000015 usually means some system file is
corrupted.  Not sure why this could be, but try restarting the system,
reinstalling Emacs, and make sure you didn't mix 32-bit and 64-bit
executables and DLLs in the same directory, or that Emacs might load
incorrect DLL because it is earlier on PATH that the correct one.

Also, maybe see it isn't your antivirus/anti-malware that interferes.

What version of Windows is that, btw?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 16:26:02 GMT) Full text and rfc822 format available.

Message #28 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Corwin Brust <corwin <at> bru.st>, Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 13:40:18 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 I tried to run it under GDB and it's giving the same message: 'No debugging symbols'. However, this time after launching Emacs 28.0.92, it produced a backtrace file which Emacs 28.1 (which was installed in my system) didn't, although the dialog showed it would produce it in the working directory. I don't know if it's of any help but I will just provide that file here.
Regards.

    On Saturday, 30 April, 2022, 04:36:35 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 
[Please use Reply All.  Please do NOT reply only to me.]

> Date: Sat, 30 Apr 2022 10:56:20 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> 
> I have been trying to debug with MSYS GDB with the link you provided but even after 2 days and hours into
> it, I could not obtain a log. GDB shows `No debugging symbols found in ./emacs.exe` everytime. I've tried to
> search the web a lot for this but I could not make it to debug. I have also tried using `-g` but it shows this
> argument is unrecognized. I am attaching a screenshot of it with this mail.

Sorry about that, and thank you for your efforts.

It looks like the Emacs binary you use was stripped of the debugging
symbols, so it doesn't support any useful debugging.

There's a pretest version that should include debug symbols, here:

  https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/emacs-28.0.92.zip

Corwin, does the pretest include debug symbols in the Emacs binary, or
was that also stripped?

If Corwin replies that debug symbols are included, could you please
install that pretest version and try running it under GDB?  TIA.
  
[Message part 2 (text/html, inline)]
[emacs_backtrace.txt (text/plain, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 16:26:03 GMT) Full text and rfc822 format available.

Message #31 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 15:46:35 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Ok, I tried using Windows Event Log. There are two errors registered after the Emacs fault event happens: 1. Application error and 2. Windows error. For both of the cases, there are two logs generated: 1. General and 2. Details.
I'm providing both as files here. For general, I am providing .txt files, one for Emacs error and one for Windows error.And for detailed logs, I am providing XML files, one for Emacs and one for Windows error.Also, screenshots are here for additional data that was shown in the Event Log.
Regards.
    On Saturday, 30 April, 2022, 07:29:56 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sat, 30 Apr 2022 13:40:18 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> I tried to run it under GDB and it's giving the same message: 'No debugging
> symbols'. However, this time after launching Emacs 28.0.92, it produced a
> backtrace file which Emacs 28.1 (which was installed in my system) didn't,
> although the dialog showed it would produce it in the working directory. I
> don't know if it's of any help but I will just provide that file here.

There should be an event logged in the Windows Event log, under
Applications, which reports some information about this abort.  Can
you look there and tell what it says?  The Event log should be
accessible by right-clicking on "Computer" and selecting "Manage".
Maybe it will tell us something helpful.
  
[Message part 2 (text/html, inline)]
[emacs_error.png (image/png, attachment)]
[emacs_log.txt (text/plain, attachment)]
[emacs.xml (text/xml, attachment)]
[win_error.png (image/png, attachment)]
[win_log.txt (text/plain, attachment)]
[win.xml (text/xml, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 16:36:02 GMT) Full text and rfc822 format available.

Message #34 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 16:34:49 +0000 (UTC)
[Message part 1 (text/plain, inline)]
Thank you. I will do that.It's Windows 10. I am also considering shifting to Linux after a while actually, since Windows is being problematic after the recent update this month.
 
   On Saturday, 30 April, 2022, 09:46:26 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sat, 30 Apr 2022 15:46:35 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
>     "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, I tried using Windows Event Log. There are two errors registered after the Emacs fault event happens:
> 1. Application error and 2. Windows error. For both of the cases, there are two logs generated: 1. General
> and 2. Details.
> I'm providing both as files here. For general, I am providing .txt files, one for Emacs error and one for
> Windows error.
> And for detailed logs, I am providing XML files, one for Emacs and one for Windows error.
> Also, screenshots are here for additional data that was shown in the Event Log.

Thanks.  Exception 0x40000015 usually means some system file is
corrupted.  Not sure why this could be, but try restarting the system,
reinstalling Emacs, and make sure you didn't mix 32-bit and 64-bit
executables and DLLs in the same directory, or that Emacs might load
incorrect DLL because it is earlier on PATH that the correct one.

Also, maybe see it isn't your antivirus/anti-malware that interferes.

What version of Windows is that, btw?
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sat, 30 Apr 2022 22:33:01 GMT) Full text and rfc822 format available.

Message #37 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Corwin Brust <corwin <at> bru.st>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 55047 <at> debbugs.gnu.org, hermit sings <hermitsings <at> yahoo.com>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 17:32:04 -0500
[Message part 1 (text/plain, inline)]
On Sat, Apr 30, 2022, 06:06 Eli Zaretskii <eliz <at> gnu.org> wrote:

>
> Corwin, does the pretest include debug symbols in the Emacs binary, or
> was that also stripped?
>

No.  I will take this as direction to avoid stripping for future pretest
versions and I'll create a binary set with debug symbols from the 28.1
source tarballs also.


>
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 00:02:01 GMT) Full text and rfc822 format available.

Message #40 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Corwin Brust <corwin <at> bru.st>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 55047 <at> debbugs.gnu.org, hermit sings <hermitsings <at> yahoo.com>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sat, 30 Apr 2022 19:00:55 -0500
On Sat, Apr 30, 2022 at 5:32 PM Corwin Brust <corwin <at> bru.st> wrote:
>
> I will [..] create a binary set with debug symbols from the 28.1 source tarballs.

Now done.  The versions without debugging symbols stripped include
"DEBUG" in the names, e.g. emacs-28.1-DEBUG.zip.  Get them from the
usual spot:

https://ftp.gnu.org/gnu/emacs/windows/emacs-28/?C=M;O=D




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 05:47:01 GMT) Full text and rfc822 format available.

Message #43 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Corwin Brust <corwin <at> bru.st>
Cc: 55047 <at> debbugs.gnu.org, hermitsings <at> yahoo.com
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 08:46:39 +0300
> From: Corwin Brust <corwin <at> bru.st>
> Date: Sat, 30 Apr 2022 17:32:04 -0500
> Cc: hermit sings <hermitsings <at> yahoo.com>, 55047 <at> debbugs.gnu.org
> 
> On Sat, Apr 30, 2022, 06:06 Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
>  Corwin, does the pretest include debug symbols in the Emacs binary, or
>  was that also stripped?
> 
> No.  I will take this as direction to avoid stripping for future pretest versions and I'll create a binary set with
> debug symbols from the 28.1 source tarballs also.

Thank you.  Indeed, at least the pretest releases should not be
stripped.

We could also consider providing a separate zip file with debugging
symbols even for the release versions (the 'objcopy' utility is
capable of moving the debug information to a separate file, and then
adding a special "debug-link" section in the executable that points to
that file, which allows GDB to debug it).




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 05:49:01 GMT) Full text and rfc822 format available.

Message #46 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Corwin Brust <corwin <at> bru.st>
Cc: 55047 <at> debbugs.gnu.org, hermitsings <at> yahoo.com
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 08:48:02 +0300
> From: Corwin Brust <corwin <at> bru.st>
> Date: Sat, 30 Apr 2022 19:00:55 -0500
> Cc: hermit sings <hermitsings <at> yahoo.com>, 55047 <at> debbugs.gnu.org
> 
> On Sat, Apr 30, 2022 at 5:32 PM Corwin Brust <corwin <at> bru.st> wrote:
> >
> > I will [..] create a binary set with debug symbols from the 28.1 source tarballs.
> 
> Now done.  The versions without debugging symbols stripped include
> "DEBUG" in the names, e.g. emacs-28.1-DEBUG.zip.  Get them from the
> usual spot:
> 
> https://ftp.gnu.org/gnu/emacs/windows/emacs-28/?C=M;O=D

Thanks.

hermitsings, could you please try running this executable under GDB
and producing a useful backtrace from it?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 09:07:01 GMT) Full text and rfc822 format available.

Message #49 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Corwin Brust <corwin <at> bru.st>, Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 09:06:34 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 
Hi,
I downloaded `emacs-28.1-DEBUG-installer.exe` and ran it twice under GDB. The first file (.png one) is the screenshot when I ran it for the first time, almost two hours ago. The second file is a .txt file which I ran some minutes ago now, after restarting the system.

Both files are attached here.
Thank you.
Just a note: It seems to me that the problem is with my system.
    On Sunday, 1 May, 2022, 11:17:59 am IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > From: Corwin Brust <corwin <at> bru.st>
> Date: Sat, 30 Apr 2022 19:00:55 -0500
> Cc: hermit sings <hermitsings <at> yahoo.com>, 55047 <at> debbugs.gnu.org
> 
> On Sat, Apr 30, 2022 at 5:32 PM Corwin Brust <corwin <at> bru.st> wrote:
> >
> > I will [..] create a binary set with debug symbols from the 28.1 source tarballs.
> 
> Now done.  The versions without debugging symbols stripped include
> "DEBUG" in the names, e.g. emacs-28.1-DEBUG.zip.  Get them from the
> usual spot:
> 
> https://ftp.gnu.org/gnu/emacs/windows/emacs-28/?C=M;O=D

Thanks.

hermitsings, could you please try running this executable under GDB
and producing a useful backtrace from it?
  
[Message part 2 (text/html, inline)]
[log.png (image/png, attachment)]
[bt.txt (text/plain, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 09:42:02 GMT) Full text and rfc822 format available.

Message #52 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 12:41:00 +0300
> Date: Sun, 1 May 2022 09:06:34 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Thread 1 (Thread 2776.0x99c):
> #0  0x00007fff7a53a104 in win32u!NtUserMsgWaitForMultipleObjectsEx () from C:\WINDOWS\System32\win32u.dll
> #1  0x00007fff7b6b0b5e in USER32!MsgWaitForMultipleObjectsEx () from C:\WINDOWS\System32\user32.dll
> #2  0x00007ff77f8a97ca in sys_select ()
> #3  0x00007ff77f869695 in really_call_select ()
> #4  0x00007ff77f86a88e in thread_select ()
> #5  0x00007ff77f8470cb in wait_reading_process_output ()
> #6  0x00007ff77f6cb56d in sit_for ()
> #7  0x00007ff77f7839a3 in read_char ()
> #8  0x00007ff77f7840f5 in read_key_sequence ()
> #9  0x00007ff77f785a4f in command_loop_1 ()
> #10 0x00007ff77f7f249d in internal_condition_case ()
> #11 0x00007ff77f77615e in command_loop_2 ()
> #12 0x00007ff77f7f240b in internal_catch ()
> #13 0x00007ff77f7760ec in command_loop ()
> #14 0x00007ff77f77c7c6 in recursive_edit_1 ()
> #15 0x00007ff77f77cb3a in Frecursive_edit ()
> #16 0x00007ff77f8e03f9 in main ()
> (gdb)

When this happens, please type these commands (the "(gdb)" part shows
the GDB prompt, no need to type it):

 (gdb) thread 1
 (gdb) frame 2
 (gdb) list
 (gdb) info locals

and post everything GDB displays as result of these commands.

Also, I see that you are attaching GDB to Emacs with "gdb -p".  This
is sub-optimal; please instead start Emacs under GDB to begin with.
Like this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"

(the quotes are important).

When GDB shows its "(gdb)" prompt, type "run" to run the program.  If
Emacs shows the abort dialog, click "YES", then type "thread apply all
bt" and show the results.  If the abort dialog doesn't pop up, you
should see GDB take control automatically when Emacs crashes; then
type "thread apply all bt" and post the results.

Thanks.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 10:14:01 GMT) Full text and rfc822 format available.

Message #55 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 10:13:38 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Ok, I ran it via GDB but it does not show the previous error which occurs while running normally in Windows.In fact, I had to exit Emacs with C-x C-c because GDB prompt was not available while Emacs was running. After closing, it shows `process exited normally`. Also, the Abort dialog did not appear while running under GDB in MSYS2.
Here is the screenshot after running.

    On Sunday, 1 May, 2022, 03:10:56 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 09:06:34 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Thread 1 (Thread 2776.0x99c):
> #0  0x00007fff7a53a104 in win32u!NtUserMsgWaitForMultipleObjectsEx () from C:\WINDOWS\System32\win32u.dll
> #1  0x00007fff7b6b0b5e in USER32!MsgWaitForMultipleObjectsEx () from C:\WINDOWS\System32\user32.dll
> #2  0x00007ff77f8a97ca in sys_select ()
> #3  0x00007ff77f869695 in really_call_select ()
> #4  0x00007ff77f86a88e in thread_select ()
> #5  0x00007ff77f8470cb in wait_reading_process_output ()
> #6  0x00007ff77f6cb56d in sit_for ()
> #7  0x00007ff77f7839a3 in read_char ()
> #8  0x00007ff77f7840f5 in read_key_sequence ()
> #9  0x00007ff77f785a4f in command_loop_1 ()
> #10 0x00007ff77f7f249d in internal_condition_case ()
> #11 0x00007ff77f77615e in command_loop_2 ()
> #12 0x00007ff77f7f240b in internal_catch ()
> #13 0x00007ff77f7760ec in command_loop ()
> #14 0x00007ff77f77c7c6 in recursive_edit_1 ()
> #15 0x00007ff77f77cb3a in Frecursive_edit ()
> #16 0x00007ff77f8e03f9 in main ()
> (gdb)

When this happens, please type these commands (the "(gdb)" part shows
the GDB prompt, no need to type it):

 (gdb) thread 1
 (gdb) frame 2
 (gdb) list
 (gdb) info locals

and post everything GDB displays as result of these commands.

Also, I see that you are attaching GDB to Emacs with "gdb -p".  This
is sub-optimal; please instead start Emacs under GDB to begin with.
Like this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"

(the quotes are important).

When GDB shows its "(gdb)" prompt, type "run" to run the program.  If
Emacs shows the abort dialog, click "YES", then type "thread apply all
bt" and show the results.  If the abort dialog doesn't pop up, you
should see GDB take control automatically when Emacs crashes; then
type "thread apply all bt" and post the results.

Thanks.
  
[Message part 2 (text/html, inline)]
[gdb.png (image/png, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 10:40:02 GMT) Full text and rfc822 format available.

Message #58 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 13:39:11 +0300
> Date: Sun, 1 May 2022 10:13:38 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
> 	"55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, I ran it via GDB but it does not show the previous error which occurs while running normally in
> Windows.
> In fact, I had to exit Emacs with C-x C-c because GDB prompt was not available while Emacs was running.
> After closing, it shows `process exited normally`. Also, the Abort dialog did not appear while running under
> GDB in MSYS2.

This becomes more and more strange.  And the warning messages shown by
GDB about a missing DLL are also not a good sign.

Try this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) set debugevents
  (gdb) run

Then post here everything GDB prints while Emacs starts up (until it
shows the initial frame) -- there should be a lot of messages about
loading DLLs.  Maybe that will tell us something.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 10:54:02 GMT) Full text and rfc822 format available.

Message #61 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 10:53:09 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Ok, here are the messages in .txt file until the initial frame showed up.
    On Sunday, 1 May, 2022, 04:09:09 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 10:13:38 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
>     "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, I ran it via GDB but it does not show the previous error which occurs while running normally in
> Windows.
> In fact, I had to exit Emacs with C-x C-c because GDB prompt was not available while Emacs was running.
> After closing, it shows `process exited normally`. Also, the Abort dialog did not appear while running under
> GDB in MSYS2.

This becomes more and more strange.  And the warning messages shown by
GDB about a missing DLL are also not a good sign.

Try this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) set debugevents
  (gdb) run

Then post here everything GDB prints while Emacs starts up (until it
shows the initial frame) -- there should be a lot of messages about
loading DLLs.  Maybe that will tell us something.
  
[Message part 2 (text/html, inline)]
[gdb_events.txt (text/plain, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 11:31:01 GMT) Full text and rfc822 format available.

Message #64 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 14:30:19 +0300
> Date: Sun, 1 May 2022 10:53:09 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
> 	"55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, here are the messages in .txt file until the initial frame showed up.

Thanks.  I see nothing new here, except that there are two exception
events reported.  So one last try:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) set debugexceptions
  (gdb) run

and post here everything that GDB shows.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 11:42:02 GMT) Full text and rfc822 format available.

Message #67 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 11:40:57 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Sure. Here is the log.
Thank you.

    On Sunday, 1 May, 2022, 05:00:19 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 10:53:09 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
>     "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Ok, here are the messages in .txt file until the initial frame showed up.

Thanks.  I see nothing new here, except that there are two exception
events reported.  So one last try:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) set debugexceptions
  (gdb) run

and post here everything that GDB shows.
  
[Message part 2 (text/html, inline)]
[gdb_events2.txt (text/plain, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 12:15:01 GMT) Full text and rfc822 format available.

Message #70 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 15:14:54 +0300
> Date: Sun, 1 May 2022 11:40:57 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
> 	"55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Starting program: C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe
> [New Thread 3876.0xff0]
> [New Thread 3876.0x2538]
> [New Thread 3876.0x14d0]
> gdb: Target exception EXCEPTION_BREAKPOINT at 0x7fff7c9a06b0
> [New Thread 3876.0xe08]
> [New Thread 3876.0x171c]
> [New Thread 3876.0x2bac]
> gdb: Target exception MS_VC_EXCEPTION at 0x7fff7a294f99
> [New Thread 3876.0x2024]
> [New Thread 3876.0x8c4]
> [New Thread 3876.0x24e0]
> [New Thread 3876.0x2e80]
> warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(1008)\Windows.ApplicationModel.dll!00007FFF724FE5CF: (caller: 00007FFF724EA25C) ReturnHr(1) tid(2bac) 80070002 The system cannot find the file specified.
> warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(512)\Windows.ApplicationModel.dll!00007FFF724FE441: (caller: 00007FFF23B87D43) ReturnHr(2) tid(2bac) 80070002 The system cannot find the file specified.

As expected.

Does Emacs still pop up the Abort dialog if you start it directly,
outside of GDB?  If it still shows Abort dialog, then you have shown a
GDB session where you attached GDB to Emacs, then said "continue", and
GDB then reported that Emacs got a SIGTRAP signal.  If at that point
you say

  (gdb) thread apply all bt

what does GDB display?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 12:33:01 GMT) Full text and rfc822 format available.

Message #73 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermitsings <at> yahoo.com
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 15:32:16 +0300
> Date: Sun, 01 May 2022 15:14:54 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
> 
> > Starting program: C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe
> > [New Thread 3876.0xff0]
> > [New Thread 3876.0x2538]
> > [New Thread 3876.0x14d0]
> > gdb: Target exception EXCEPTION_BREAKPOINT at 0x7fff7c9a06b0
> > [New Thread 3876.0xe08]
> > [New Thread 3876.0x171c]
> > [New Thread 3876.0x2bac]
> > gdb: Target exception MS_VC_EXCEPTION at 0x7fff7a294f99
> > [New Thread 3876.0x2024]
> > [New Thread 3876.0x8c4]
> > [New Thread 3876.0x24e0]
> > [New Thread 3876.0x2e80]
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(1008)\Windows.ApplicationModel.dll!00007FFF724FE5CF: (caller: 00007FFF724EA25C) ReturnHr(1) tid(2bac) 80070002 The system cannot find the file specified.
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(512)\Windows.ApplicationModel.dll!00007FFF724FE441: (caller: 00007FFF23B87D43) ReturnHr(2) tid(2bac) 80070002 The system cannot find the file specified.
> 
> As expected.

Wait a minute: didn't you say this is Windows 10?  If so, why are we
emitting MS_VC_EXCEPTION, that is only done on older Windows versions.

And why do we try to set the name of some thread?

Are you running "emacs -Q", or are you running without the -Q switch,
i.e. with all your customizations?  If the latter, could it be that
some of the customizations start Lisp threads?  If you run Emacs like
this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) break sys_thread_set_name
  (gdb) run

does the breakpoint in sys_thread_set_name break?  If so, please type

  (gdb) bt

when Emacs is stopped in sys_thread_set_name, and show the result.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:18:02 GMT) Full text and rfc822 format available.

Message #76 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 13:17:00 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Yes, it is still showing the Abort dialog. In the dialog, there are two options: 1. Debug Emacs by attaching it with GDB only via `pid`  and   2. produce a backtrace file in the current directory.So, last time I opted for the first one using `pid`, it showed SIGTRAP. However, now GDB is debugging very slowly and is taking a lot of time. Even after that, SIGTRAP didn't show up this time. 

That's why, I could not reply back here.
    On Sunday, 1 May, 2022, 05:44:51 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 11:40:57 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
>     "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Starting program: C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe
> [New Thread 3876.0xff0]
> [New Thread 3876.0x2538]
> [New Thread 3876.0x14d0]
> gdb: Target exception EXCEPTION_BREAKPOINT at 0x7fff7c9a06b0
> [New Thread 3876.0xe08]
> [New Thread 3876.0x171c]
> [New Thread 3876.0x2bac]
> gdb: Target exception MS_VC_EXCEPTION at 0x7fff7a294f99
> [New Thread 3876.0x2024]
> [New Thread 3876.0x8c4]
> [New Thread 3876.0x24e0]
> [New Thread 3876.0x2e80]
> warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(1008)\Windows.ApplicationModel.dll!00007FFF724FE5CF: (caller: 00007FFF724EA25C) ReturnHr(1) tid(2bac) 80070002 The system cannot find the file specified.
> warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(512)\Windows.ApplicationModel.dll!00007FFF724FE441: (caller: 00007FFF23B87D43) ReturnHr(2) tid(2bac) 80070002 The system cannot find the file specified.

As expected.

Does Emacs still pop up the Abort dialog if you start it directly,
outside of GDB?  If it still shows Abort dialog, then you have shown a
GDB session where you attached GDB to Emacs, then said "continue", and
GDB then reported that Emacs got a SIGTRAP signal.  If at that point
you say

  (gdb) thread apply all bt

what does GDB display?
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:25:01 GMT) Full text and rfc822 format available.

Message #79 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 13:24:31 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 No, I'm launching it from the Start Menu as an application.

Yes, the breakpoint breaks at one point. But `bt` shows `No stack`.
I've attached a screenshot of it.

    On Sunday, 1 May, 2022, 06:02:40 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 01 May 2022 15:14:54 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
> 
> > Starting program: C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe
> > [New Thread 3876.0xff0]
> > [New Thread 3876.0x2538]
> > [New Thread 3876.0x14d0]
> > gdb: Target exception EXCEPTION_BREAKPOINT at 0x7fff7c9a06b0
> > [New Thread 3876.0xe08]
> > [New Thread 3876.0x171c]
> > [New Thread 3876.0x2bac]
> > gdb: Target exception MS_VC_EXCEPTION at 0x7fff7a294f99
> > [New Thread 3876.0x2024]
> > [New Thread 3876.0x8c4]
> > [New Thread 3876.0x24e0]
> > [New Thread 3876.0x2e80]
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(1008)\Windows.ApplicationModel.dll!00007FFF724FE5CF: (caller: 00007FFF724EA25C) ReturnHr(1) tid(2bac) 80070002 The system cannot find the file specified.
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(512)\Windows.ApplicationModel.dll!00007FFF724FE441: (caller: 00007FFF23B87D43) ReturnHr(2) tid(2bac) 80070002 The system cannot find the file specified.
> 
> As expected.

Wait a minute: didn't you say this is Windows 10?  If so, why are we
emitting MS_VC_EXCEPTION, that is only done on older Windows versions.

And why do we try to set the name of some thread?

Are you running "emacs -Q", or are you running without the -Q switch,
i.e. with all your customizations?  If the latter, could it be that
some of the customizations start Lisp threads?  If you run Emacs like
this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) break sys_thread_set_name
  (gdb) run

does the breakpoint in sys_thread_set_name break?  If so, please type

  (gdb) bt

when Emacs is stopped in sys_thread_set_name, and show the result.
  
[Message part 2 (text/html, inline)]
[break.png (image/png, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:27:02 GMT) Full text and rfc822 format available.

Message #82 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 13:26:25 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Also, sometimes (not always) after startup and before the Abort dialog shows up, I get this message in Emacs:`Error: Internal native compiler error failed to compile`.
 
    On Sunday, 1 May, 2022, 06:54:31 pm IST, hermit sings <hermitsings <at> yahoo.com> wrote:  
 
  No, I'm launching it from the Start Menu as an application.

Yes, the breakpoint breaks at one point. But `bt` shows `No stack`.
I've attached a screenshot of it.

    On Sunday, 1 May, 2022, 06:02:40 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 01 May 2022 15:14:54 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
> 
> > Starting program: C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe
> > [New Thread 3876.0xff0]
> > [New Thread 3876.0x2538]
> > [New Thread 3876.0x14d0]
> > gdb: Target exception EXCEPTION_BREAKPOINT at 0x7fff7c9a06b0
> > [New Thread 3876.0xe08]
> > [New Thread 3876.0x171c]
> > [New Thread 3876.0x2bac]
> > gdb: Target exception MS_VC_EXCEPTION at 0x7fff7a294f99
> > [New Thread 3876.0x2024]
> > [New Thread 3876.0x8c4]
> > [New Thread 3876.0x24e0]
> > [New Thread 3876.0x2e80]
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(1008)\Windows.ApplicationModel.dll!00007FFF724FE5CF: (caller: 00007FFF724EA25C) ReturnHr(1) tid(2bac) 80070002 The system cannot find the file specified.
> > warning: onecore\base\appmodel\runtime\winrt\lib\windows.applicationmodel.package.cpp(512)\Windows.ApplicationModel.dll!00007FFF724FE441: (caller: 00007FFF23B87D43) ReturnHr(2) tid(2bac) 80070002 The system cannot find the file specified.
> 
> As expected.

Wait a minute: didn't you say this is Windows 10?  If so, why are we
emitting MS_VC_EXCEPTION, that is only done on older Windows versions.

And why do we try to set the name of some thread?

Are you running "emacs -Q", or are you running without the -Q switch,
i.e. with all your customizations?  If the latter, could it be that
some of the customizations start Lisp threads?  If you run Emacs like
this:

  gdb "C:\Program Files\Emacs\emacs-28.1\bin\emacs.exe"
  ...
  (gdb) break sys_thread_set_name
  (gdb) run

does the breakpoint in sys_thread_set_name break?  If so, please type

  (gdb) bt

when Emacs is stopped in sys_thread_set_name, and show the result.
    
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:27:02 GMT) Full text and rfc822 format available.

Message #85 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 16:26:38 +0300
> Date: Sun, 1 May 2022 13:17:00 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
> 	"55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Yes, it is still showing the Abort dialog. In the dialog, there are two options: 1. Debug Emacs by attaching it
> with GDB only via `pid`  and   2. produce a backtrace file in the current directory.
> So, last time I opted for the first one using `pid`, it showed SIGTRAP. However, now GDB is debugging very
> slowly and is taking a lot of time.

This is expected.

> Even after that, SIGTRAP didn't show up this time. 

What did show, then?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:34:02 GMT) Full text and rfc822 format available.

Message #88 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 16:33:41 +0300
> Date: Sun, 1 May 2022 13:24:31 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> No, I'm launching it from the Start Menu as an application.

And if you open a Command Prompt window and invoke Emacs from the cmd
prompt, as "emacs -Q", does it also show the abort dialog?

Also, what happens if you invoke it from the Start->Run dialog, like
this:

  C:\Program Files\Emacs\emacs-28.1\bin\runemacs.exe -Q

(note: "runemacs", not "emacs").

> Yes, the breakpoint breaks at one point. But `bt` shows `No stack`.

That's because you haven't run the application yet, by typing "run".

But I see that after you do run it, the breakpoint never breaks.  So I
still don't understand why you see that MS_VC_EXCEPTION event; it
doesn't happen here, FWIW.

What happens if instead of "run" at the GDB prompt you type "run -Q"?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:36:01 GMT) Full text and rfc822 format available.

Message #91 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 16:35:34 +0300
> Date: Sun, 1 May 2022 13:26:25 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> Also, sometimes (not always) after startup and before the Abort dialog shows up, I get this message in
> Emacs:
> `Error: Internal native compiler error failed to compile`.

That's expected: you probably don't have GCC and Binutils installed,
so you cannot natively-compile Lisp that was not already compiled.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 13:43:01 GMT) Full text and rfc822 format available.

Message #94 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 13:41:54 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 It runs very slow compared to how it ran previously and produce SIGTRAP after clicking 'Yes' on the Abort dialog.
It continues to show this message, repeating itself with changed new threads.

A screenshot:

    On Sunday, 1 May, 2022, 06:56:47 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 13:17:00 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "corwin <at> bru.st" <corwin <at> bru.st>, 
>     "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>
> 
> Yes, it is still showing the Abort dialog. In the dialog, there are two options: 1. Debug Emacs by attaching it
> with GDB only via `pid`  and  2. produce a backtrace file in the current directory.
> So, last time I opted for the first one using `pid`, it showed SIGTRAP. However, now GDB is debugging very
> slowly and is taking a lot of time.

This is expected.

> Even after that, SIGTRAP didn't show up this time. 

What did show, then?
  
[Message part 2 (text/html, inline)]
[no_sigtrap.png (image/png, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 14:19:02 GMT) Full text and rfc822 format available.

Message #97 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 14:18:28 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 If I invoke `emacs -Q`, it opens up a buffer: *scratch*.But if I do `emacs -q`, it opens Emacs but without customization, I'd guess.This happens in all three cases: 1. from Command Prompt    2. via Run (even with `runemacs.exe`)   and   3. via GDB 

The Abort dialog appears in the first two cases (after emacs -q).
However, it does not appear in if run via GDB. For GDB, I've attached a screenshot of the result.
    On Sunday, 1 May, 2022, 07:03:12 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 13:24:31 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> 
> No, I'm launching it from the Start Menu as an application.

And if you open a Command Prompt window and invoke Emacs from the cmd
prompt, as "emacs -Q", does it also show the abort dialog?

Also, what happens if you invoke it from the Start->Run dialog, like
this:

  C:\Program Files\Emacs\emacs-28.1\bin\runemacs.exe -Q

(note: "runemacs", not "emacs").

> Yes, the breakpoint breaks at one point. But `bt` shows `No stack`.

That's because you haven't run the application yet, by typing "run".

But I see that after you do run it, the breakpoint never breaks.  So I
still don't understand why you see that MS_VC_EXCEPTION event; it
doesn't happen here, FWIW.

What happens if instead of "run" at the GDB prompt you type "run -Q"?
  
[Message part 2 (text/html, inline)]
[run-q.png (image/png, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 14:33:02 GMT) Full text and rfc822 format available.

Message #100 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 17:32:49 +0300
> Date: Sun, 1 May 2022 14:18:28 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> If I invoke `emacs -Q`, it opens up a buffer: *scratch*.
> But if I do `emacs -q`, it opens Emacs but without customization, I'd guess.
> This happens in all three cases: 1. from Command Prompt    2. via Run (even with `runemacs.exe`)   and  
> 3. via GDB 
> 
> The Abort dialog appears in the first two cases (after emacs -q).
> However, it does not appear in if run via GDB. For GDB, I've attached a screenshot of the result.

So in the first two cases, Emacs displays *scratch* (for -Q) or the
splash screen (for -q), and _then_ shows the Abort dialog?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 14:40:02 GMT) Full text and rfc822 format available.

Message #103 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 14:39:37 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Yes, now that I think of it, it doesn't show Abort dialog while displaying the scratch buffer.
But if `-q` is used, it does, like if I'd have normally opened it.   On Sunday, 1 May, 2022, 08:02:46 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 14:18:28 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> 
> If I invoke `emacs -Q`, it opens up a buffer: *scratch*.
> But if I do `emacs -q`, it opens Emacs but without customization, I'd guess.
> This happens in all three cases: 1. from Command Prompt    2. via Run (even with `runemacs.exe`)  and  
> 3. via GDB 
> 
> The Abort dialog appears in the first two cases (after emacs -q).
> However, it does not appear in if run via GDB. For GDB, I've attached a screenshot of the result.

So in the first two cases, Emacs displays *scratch* (for -Q) or the
splash screen (for -q), and _then_ shows the Abort dialog?
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 14:44:02 GMT) Full text and rfc822 format available.

Message #106 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 14:43:08 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Also, just to add in, the previous version: Emacs 27.2 is working fine on the system and no Abort dialog is shown.I just installed it and checked.

    On Sunday, 1 May, 2022, 08:09:38 pm IST, hermit sings <hermitsings <at> yahoo.com> wrote:  
 
  Yes, now that I think of it, it doesn't show Abort dialog while displaying the scratch buffer.
But if `-q` is used, it does, like if I'd have normally opened it.   On Sunday, 1 May, 2022, 08:02:46 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 14:18:28 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> 
> If I invoke `emacs -Q`, it opens up a buffer: *scratch*.
> But if I do `emacs -q`, it opens Emacs but without customization, I'd guess.
> This happens in all three cases: 1. from Command Prompt    2. via Run (even with `runemacs.exe`)  and  
> 3. via GDB 
> 
> The Abort dialog appears in the first two cases (after emacs -q).
> However, it does not appear in if run via GDB. For GDB, I've attached a screenshot of the result.

So in the first two cases, Emacs displays *scratch* (for -Q) or the
splash screen (for -q), and _then_ shows the Abort dialog?
    
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 14:56:02 GMT) Full text and rfc822 format available.

Message #109 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 17:55:57 +0300
> Date: Sun, 1 May 2022 14:39:37 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> Yes, now that I think of it, it doesn't show Abort dialog while displaying the scratch buffer.
> But if `-q` is used, it does, like if I'd have normally opened it.

What if you replace your .emacs init file with an empty file, and then
invoke Emacs without -Q or -q?

And another experiment: start Emacs with -Q, wait until it shows the
*scratch* buffer, and then type

  C-x C-f C:/Program Files/Emacs/emacs-28.1/share/emacs/28.1/etc/images/splash.svg RET

Does it show the abort dialog after you press RET in the above
command?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 15:23:02 GMT) Full text and rfc822 format available.

Message #112 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 15:22:21 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 I actually didn't know about the emacs init file. But I searched for it on the web. I understand that it should be in `.emacs.d` in 'AppData\Roaming' folder in Windows?But there was none. So according to an answer I read on Stackoverflow, I created a file `init.el` and left it blank.Then started Emacs normally and via Command Prompt. It still, however, shows the Abort dialog for both.

For the second one: yes! It starts showing the Abort dialog after displaying the `splash.svg`.

    On Sunday, 1 May, 2022, 08:25:54 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 14:39:37 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> 
> Yes, now that I think of it, it doesn't show Abort dialog while displaying the scratch buffer.
> But if `-q` is used, it does, like if I'd have normally opened it.

What if you replace your .emacs init file with an empty file, and then
invoke Emacs without -Q or -q?

And another experiment: start Emacs with -Q, wait until it shows the
*scratch* buffer, and then type

  C-x C-f C:/Program Files/Emacs/emacs-28.1/share/emacs/28.1/etc/images/splash.svg RET

Does it show the abort dialog after you press RET in the above
command?
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 15:30:02 GMT) Full text and rfc822 format available.

Message #115 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 18:29:37 +0300
> Date: Sun, 1 May 2022 15:22:21 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> I actually didn't know about the emacs init file. But I searched for it on the web. I understand that it should be
> in `.emacs.d` in 'AppData\Roaming' folder in Windows?
> But there was none. So according to an answer I read on Stackoverflow, I created a file `init.el` and left it
> blank.
> Then started Emacs normally and via Command Prompt. It still, however, shows the Abort dialog for both.
> 
> For the second one: yes! It starts showing the Abort dialog after displaying the `splash.svg`.

So this seems to be related to librsvg, the library used to display
SVG images, or some of its dependencies.

What happens if you start with -Q, and then do this:

  C-x C-f C:/Program Files/Emacs/emacs-28.1/share/emacs/28.1/etc/images/splash.png RET

That is, ask Emacs to display the splash image in PNG format?  Please
also try with splash.xpm and splash.pbm.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 15:50:02 GMT) Full text and rfc822 format available.

Message #118 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 15:48:54 +0000 (UTC)
[Message part 1 (text/plain, inline)]
 Yes, the Abort dialog appears for each case, after displaying the image.

    On Sunday, 1 May, 2022, 08:59:32 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 15:22:21 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> 
> I actually didn't know about the emacs init file. But I searched for it on the web. I understand that it should be
> in `.emacs.d` in 'AppData\Roaming' folder in Windows?
> But there was none. So according to an answer I read on Stackoverflow, I created a file `init.el` and left it
> blank.
> Then started Emacs normally and via Command Prompt. It still, however, shows the Abort dialog for both.
> 
> For the second one: yes! It starts showing the Abort dialog after displaying the `splash.svg`.

So this seems to be related to librsvg, the library used to display
SVG images, or some of its dependencies.

What happens if you start with -Q, and then do this:

  C-x C-f C:/Program Files/Emacs/emacs-28.1/share/emacs/28.1/etc/images/splash.png RET

That is, ask Emacs to display the splash image in PNG format?  Please
also try with splash.xpm and splash.pbm.
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 16:10:02 GMT) Full text and rfc822 format available.

Message #121 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 19:09:54 +0300
> Date: Sun, 1 May 2022 15:48:54 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> Yes, the Abort dialog appears for each case, after displaying the image.

Thanks.

I'm more or less at the end of my wits.  The only advice I can give is
to always run Emacs under GDB, where you say it doesn't show the abort
dialog.

Sorry.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 16:20:02 GMT) Full text and rfc822 format available.

Message #124 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: hermit sings <hermitsings <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>,
 "corwin <at> bru.st" <corwin <at> bru.st>
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 1 May 2022 16:19:27 +0000 (UTC)
[Message part 1 (text/plain, inline)]
No no, please. Thank you for taking the time and putting so much effort into my problem. I really really appreciate it a lot.Corwin Brust, too.I'll take the advice, thanks. I'm also considering switching back to Linux which I was using at an earlier time.I really learned a lot from the conversations and I hope my problem is not happening to anyone else.On the bright side, I can still use Emacs 27.2 as it is running normally.But I do appreciate the response I got from you and GNU community. Thank you.

Regards.
   On Sunday, 1 May, 2022, 09:39:49 pm IST, Eli Zaretskii <eliz <at> gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 15:48:54 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
>     "corwin <at> bru.st" <corwin <at> bru.st>
> Yes, the Abort dialog appears for each case, after displaying the image.

Thanks.

I'm more or less at the end of my wits.  The only advice I can give is
to always run Emacs under GDB, where you say it doesn't show the abort
dialog.

Sorry.
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Sun, 01 May 2022 16:46:02 GMT) Full text and rfc822 format available.

Message #127 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermit sings <hermitsings <at> yahoo.com>
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Sun, 01 May 2022 19:45:38 +0300
> Date: Sun, 1 May 2022 16:19:27 +0000 (UTC)
> From: hermit sings <hermitsings <at> yahoo.com>
> Cc: "55047 <at> debbugs.gnu.org" <55047 <at> debbugs.gnu.org>, 
> 	"corwin <at> bru.st" <corwin <at> bru.st>
> 
> No no, please. Thank you for taking the time and putting so much effort into my problem. I really really
> appreciate it a lot.
> Corwin Brust, too.
> I'll take the advice, thanks. I'm also considering switching back to Linux which I was using at an earlier time.
> I really learned a lot from the conversations and I hope my problem is not happening to anyone else.
> On the bright side, I can still use Emacs 27.2 as it is running normally.
> But I do appreciate the response I got from you and GNU community. Thank you.

You are welcome.

If no new data and no new ideas will pop up in a week or so, I will
close the bug.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#55047; Package emacs. (Tue, 17 May 2022 13:32:02 GMT) Full text and rfc822 format available.

Message #130 received at 55047 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: hermitsings <at> yahoo.com
Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
Subject: Re: bug#55047: Bug: Abort Dialog upon start
Date: Tue, 17 May 2022 16:30:10 +0300
tags 55047 unreproducible
close 55047
thanks

> Date: Sun, 01 May 2022 19:45:38 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 55047 <at> debbugs.gnu.org, corwin <at> bru.st
> 
> If no new data and no new ideas will pop up in a week or so, I will
> close the bug.

Done.




Added tag(s) unreproducible. Request was from Eli Zaretskii <eliz <at> gnu.org> to control <at> debbugs.gnu.org. (Tue, 17 May 2022 13:32:02 GMT) Full text and rfc822 format available.

bug closed, send any further explanations to 55047 <at> debbugs.gnu.org and hermit sings <hermitsings <at> yahoo.com> Request was from Eli Zaretskii <eliz <at> gnu.org> to control <at> debbugs.gnu.org. (Tue, 17 May 2022 13:32:03 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 15 Jun 2022 11:24:07 GMT) Full text and rfc822 format available.

This bug report was last modified 1 year and 287 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.