From: Lars Ingebrigtsen <larsi@gnus.org>
To: Scott Otterson <scotto@sharpleaf.org>
Cc: 51758@debbugs.gnu.org, 'Eli Zaretskii' <eliz@gnu.org>
Subject: bug#51758: 27.2; Backtrace put in home dir, not current dir
Date: Tue, 20 Sep 2022 14:22:04 +0200 [thread overview]
Message-ID: <87bkrajkwj.fsf@gnus.org> (raw)
In-Reply-To: <CAPY3P0S_z0kggyNGxLy7xbYy_o5uuefaKzJ=KFHFy6aCiCvHbg@mail.gmail.com> (Scott Otterson's message of "Wed, 10 Nov 2021 15:36:39 -0800")
Scott Otterson <scotto@sharpleaf.org> writes:
> When emacs crashes, I get an error popup (attached) saying that if I click NO, emacs
> will abort and put emacs_backtrace.txt in "the current directory."
>
> Clicking NO, does produce emacs_backtrace.txt (attached), but it's actually put in my
> EMACSHOME dir (the one emacs understands as "~"), not the current dir.
I guess this is from w32fns.c:
button = MessageBox (NULL,
"A fatal error has occurred!\n\n"
"Would you like to attach a debugger?\n\n"
"Select:\n"
"YES -- to debug Emacs, or\n"
"NO -- to abort Emacs and produce a backtrace\n"
" (emacs_backtrace.txt in current directory)."
#if __GNUC__
"\n\n(type \"gdb -p <emacs-PID>\" and\n"
"\"continue\" inside GDB before clicking YES.)"
#endif
, "Emacs Abort Dialog",
Eli, should that text just be amended? (If it always puts the backtrace
in EMACSHOME, that is -- I haven't actually cheked the code here.)
next prev parent reply other threads:[~2022-09-20 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 23:36 bug#51758: 27.2; Backtrace put in home dir, not current dir Scott Otterson
2022-09-20 12:22 ` Lars Ingebrigtsen [this message]
2022-09-20 12:45 ` Eli Zaretskii
2022-09-20 13:05 ` Lars Ingebrigtsen
2022-09-20 14:13 ` Scott Otterson
2022-09-20 14:24 ` Eli Zaretskii
2022-09-20 14:52 ` Lars Ingebrigtsen
2022-09-20 15:48 ` Eli Zaretskii
2022-09-20 17:02 ` Scott Otterson
2022-09-20 17:28 ` Eli Zaretskii
2022-09-20 18:14 ` Scott Otterson
[not found] ` <CAPY3P0Tj-GpVyZZ4KgSS8KKvOx+R5KJjbCP2C-UPGtMY98MLUg@mail.gmail.com>
2022-09-20 15:42 ` Eli Zaretskii
2022-09-20 15:45 ` Lars Ingebrigtsen
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=87bkrajkwj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51758@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=scotto@sharpleaf.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 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).