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@gnu.org> wrote:  
 
 > Date: Sun, 1 May 2022 11:40:57 +0000 (UTC)
> From: hermit sings <hermitsings@yahoo.com>
> Cc: "corwin@bru.st" <corwin@bru.st>, 
>     "55047@debbugs.gnu.org" <55047@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?