unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13968@debbugs.gnu.org
Subject: bug#13968: 24.3.50; emacs_backtrace.txt
Date: Sat, 16 Mar 2013 09:17:31 +0200	[thread overview]
Message-ID: <831ubf4xv8.fsf@gnu.org> (raw)
In-Reply-To: <FACDB8B7794343D1933C24425E96F9F1@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <13968@debbugs.gnu.org>
> Date: Fri, 15 Mar 2013 14:34:09 -0700
> 
> > > Useless without a recipe.
> > 
> > Forgot to show where it aborts:
> > 
> > 	  form.rcArea.bottom = (WINDOW_BOTTOM_EDGE_Y (w)
> > 				- WINDOW_MODE_LINE_HEIGHT (w));
> > 
> > It's an assertion violation, but the report doesn't even say what was
> > the text of the assertion message.  The above 2 macros could abort in
> > XFRAME, XWINDOW, or XBUFFER.
> 
> Yes, well there never is a recipe for this kind of thing

As I probably already said, they are probably related to your heavy
use of separate and minibuffer-less frames.  But this conclusion is
not instrumental to fixing those aborts, without a clear recipe to
reproduce a similar problem and/or without the ability to look around
when the abort does happen.  I urge you (again) to run Emacs from GDB
and leave the GDB session running long enough for us to ask you to
investigate after the abort.

> What's the point of adding such assertions and providing backtraces that are
> apparently useless?

The assertions are not specific to the aborts you experience.  They
are part of C macros, such as XWINDOW and XBUFFER, which extract C
data structures from a Lisp object.  These macros are used all over
the code.

> Anyway, multiple reports of crashes (by me and others) have not prevented Emacs
> 24.2 or 24.3 from being released.

In a release version, these assertions are not compiled into the
binary.

> FWIW, before Emacs 24 I rarely had an Emacs crash.

Probably because pretest and snapshot binaries before that were not
compiled with these assertions.

> Presumably such assertions are turned off when Emacs is released (?)

Yes.

> As you hint above, perhaps the assertions can be refined, so the backtraces
> produced become more informative.  I will continue to report them, unless you
> say it's not worth the trouble in general.

Please continue reporting them.  However, it will be much more useful
if you could let us investigate by using GDB.





      reply	other threads:[~2013-03-16  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 20:59 bug#13968: 24.3.50; emacs_backtrace.txt Drew Adams
2013-03-15 21:06 ` Eli Zaretskii
2013-03-15 21:19   ` Eli Zaretskii
2013-03-15 21:34     ` Drew Adams
2013-03-16  7:17       ` Eli Zaretskii [this message]

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=831ubf4xv8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13968@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).