all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Liam Stitt <stittl@cuug.ab.ca>
Cc: 44047@debbugs.gnu.org
Subject: bug#44047: current HEAD has been crashing on startup
Date: Mon, 19 Oct 2020 17:23:26 +0300	[thread overview]
Message-ID: <83wnzmpa5d.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2010181902290.25328@arnold.cuug.ab.ca> (message from Liam Stitt on Sun, 18 Oct 2020 19:10:12 -0600 (MDT))

> Date: Sun, 18 Oct 2020 19:10:12 -0600 (MDT)
> From: Liam Stitt <stittl@cuug.ab.ca>
> cc: 44047@debbugs.gnu.org
> 
> > Can you build an unoptimized version, run it under GDB, and when it
> > crashes, show a backtrace?
> 
> Does building the unoptimized version require more than tweaking the 
> CFLAGS entry in src/Makefile? If not, this is what I got:

Thanks.  Please reproduce the crash again, and this time say

  (gdb) bt full

and post everything that produces.

> 0x0000555555598126 in fill_up_frame_row_with_spaces (row=0x100, upto=0)
                                                       ^^^
That 'row' pointer is clearly bogus (and causes the crash).  The
question is how does this happen.  I hope the output of "bt full" will
give some ideas.

Thanks.

P.S. Is this on some terminal emulator?  If so, which one (xterm,
something else?), and what are the dimensions of the terminal window
where you invoke Emacs?





  reply	other threads:[~2020-10-19 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 17:06 bug#44047: current HEAD has been crashing on startup Liam Stitt
2020-10-17 17:15 ` Eli Zaretskii
2020-10-19  1:10   ` Liam Stitt
2020-10-19 14:23     ` Eli Zaretskii [this message]
2020-10-19 16:28       ` Liam Stitt
2020-10-19 17:08         ` Eli Zaretskii
2020-10-20  4:39           ` Liam Stitt
2020-10-20 15:48             ` Eli Zaretskii
2020-10-20 22:19               ` Liam Stitt
2020-10-21 16:03                 ` Eli Zaretskii
2020-10-26 15:12                   ` Eli Zaretskii
2020-11-01 13:48                     ` Liam Stitt
2020-11-01 15:34                       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wnzmpa5d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44047@debbugs.gnu.org \
    --cc=stittl@cuug.ab.ca \
    /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.