From: Shuguang Sun <shuguang79@qq.com>
To: help-gnu-emacs@gnu.org
Subject: How to debug/gdb emacs/runemacs in windows?
Date: Thu, 23 May 2019 16:15:56 +0800 [thread overview]
Message-ID: <vk5y7eahy4ar.fsf@qq.com> (raw)
Hi all,
My emacs (pdumper) crashes for some commands, and I'd like to do some
debug/gdb to find more information.
First, I run gdb in msys2/mingw64:
--8<---------------cut here---------------start------------->8---
# gdb emacs
GNU gdb (GDB) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from emacs...
(gdb) run --dump-file "c:/Users/username/HOME/.emacs.d/var/dumps/semacs.pdmp" --force-dump
Starting program: C:\Users\username\emacs\bin\emacs.exe --dump-file "c:/Users/username/HOME/.emacs.d/var/dumps/semacs.pdmp" --force-dump
[New Thread 231988.0x38e2c]
[New Thread 231988.0x3ea30]
[New Thread 231988.0x3d88c]
[Thread 231988.0x38e2c exited with code 0]
[Thread 231988.0x3ea30 exited with code 0]
[Thread 231988.0x3d88c exited with code 0]
[New Thread 231988.0x3b6c4]
[New Thread 231988.0x35dd0]
[New Thread 231988.0x3bb88]
[Thread 231988.0x3bb88 exited with code 1]
[New Thread 231988.0x22c0]
[Thread 231988.0x22c0 exited with code 1]
Thread 1 received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
--8<---------------cut here---------------end--------------->8---
The error above is because I call `recentf-edit-list` in the pdumper
emacs which make it crash. Then
--8<---------------cut here---------------start------------->8---
(gdb) thread 1
[Switching to thread 1 (Thread 231988.0x3954c)]
#0 0x0000000000000000 in ?? ()
(gdb) backtrace
#0 0x0000000000000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
--8<---------------cut here---------------end--------------->8---
How could I find more information?
--
Best Regards
Shuguang Sun
next reply other threads:[~2019-05-23 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 8:15 Shuguang Sun [this message]
2019-05-23 14:13 ` How to debug/gdb emacs/runemacs in windows? Eli Zaretskii
2019-05-24 1:26 ` Shuguang Sun
2019-05-24 4:43 ` Shuguang Sun
2019-05-27 9:37 ` Shuguang Sun
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=vk5y7eahy4ar.fsf@qq.com \
--to=shuguang79@qq.com \
--cc=help-gnu-emacs@gnu.org \
/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.