From: Eli Zaretskii <eliz@gnu.org>
To: Madhu <enometh@meer.net>
Cc: emacs-devel@gnu.org
Subject: Re: another unhelpful backtrace from redisplay-internal
Date: Sat, 07 Mar 2020 18:14:22 +0200 [thread overview]
Message-ID: <83a74s9m75.fsf@gnu.org> (raw)
In-Reply-To: <m336ak6uzv.fsf@leonis4.robolove.meer.net> (message from Madhu on Sat, 07 Mar 2020 21:02:36 +0530)
> From: Madhu <enometh@meer.net>
> Date: Sat, 07 Mar 2020 21:02:36 +0530
>
> I have a sure recipe for a crash in recent emacs but the configuration
> is complex and I'm afraid I don't have a simple test case. I'm posting
> the initial backtrace here in case anyone can suggest things I should
> look for, or some ways I could narrow it down.
"Recent emacs" from which branch of the repository? Also, how recent?
(Crashes should be reported with "M-x report-emacs-bug", as there's no
doubt they are bugs of some sort, and therefore no reason to discuss
them here. Using report-emacs-bug would have included all the
information I'm asking about above, automatically.)
> Emacs is compiled with -g3 -O2, and I'm not sure if all the info to
> debug this is available.
The backtrace shows incorrect files and lines, and most values are
"optimized out" (and others are therefore suspect to not be the
truth).
> Any suggestions please?
Rebuild without optimizations and try reproducing the problem with
your recipe. If successful, post the backtrace.
Thanks.
next prev parent reply other threads:[~2020-03-07 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 15:32 another unhelpful backtrace from redisplay-internal Madhu
2020-03-07 16:14 ` Eli Zaretskii [this message]
2020-03-07 16:25 ` Eli Zaretskii
2020-03-07 17:46 ` Madhu
2020-03-07 17:47 ` Madhu
2020-03-07 18:04 ` 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=83a74s9m75.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
/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).