unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: lekktu@gmail.com, 14062@debbugs.gnu.org
Subject: bug#14062: 24.3.50; emacs_backtrace.txt
Date: Mon, 15 Apr 2013 19:21:24 +0300	[thread overview]
Message-ID: <83obdf69yz.fsf@gnu.org> (raw)
In-Reply-To: <516C2276.3020006@gmx.at>

> Date: Mon, 15 Apr 2013 17:53:26 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: drew.adams@oracle.com, lekktu@gmail.com, 14062@debbugs.gnu.org
> 
>  > Only a non-leaf window can have its w->contents be something other
>  > than a buffer, right?  If BUFFERP(w->contents) returns zero
> 
> ... for an internal window w->contents _must_ be another window, only
> for deleted windows this can be nil (but Dmitry would have to verify
> this, I didn't look at his last changes yet) ...

But for nil, BUFFERP will return zero, and the code that uses XBUFFER
should not be called, IMO.

>  > and
>  > XBUFFER hits an assertion violation, what else can this window be
>  > except non-leaf?
> 
> A window with an uninitialized contents field.  Such windows exist from
> the moment they are allocated by make_window until they either get a
> child or a buffer in the contents field.

But the uninitialized contents field should be zero, no?  Again, it
should not pass the BUFFERP test.

So the mystery still stands.

>  > I don't think so.  I examined the preprocessed source, and didn't see
>  > any instance of missing parentheses.  I added some just so someone who
>  > looks at the macros won't wonder, like I did, whether this could be
>  > the problem.
>  >
>  > But even if you are right, and the problem will now disappear, we can
>  > still resolve this bug by simply going back to the original code.
> 
> I don't think the problem will disappear this way.

Neither do I.





  reply	other threads:[~2013-04-15 16:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 23:33 bug#14062: 24.3.50; emacs_backtrace.txt Drew Adams
2013-03-27  6:57 ` Eli Zaretskii
2013-03-27  9:45   ` Dani Moncayo
2013-03-27 12:20     ` Eli Zaretskii
2013-03-27 13:39       ` Drew Adams
2013-03-28  9:25         ` Eli Zaretskii
2013-04-15  7:35           ` Eli Zaretskii
2013-04-15 11:54             ` Juanma Barranquero
2013-04-15 12:30               ` Eli Zaretskii
2013-04-15 12:40             ` martin rudalics
2013-04-15 14:18               ` Eli Zaretskii
2013-04-15 15:53                 ` martin rudalics
2013-04-15 16:21                   ` Eli Zaretskii [this message]
2013-04-15 19:22                     ` martin rudalics
2013-04-16  6:08                       ` Eli Zaretskii
2013-04-22 16:04                         ` Drew Adams
2013-04-22 16:12                           ` Juanma Barranquero
2013-04-22 18:05                             ` Eli Zaretskii
2013-04-22 18:18                               ` Drew Adams
2013-05-04 10:27                               ` Eli Zaretskii
2013-05-04 12:27                                 ` martin rudalics
2013-05-04 12:33                                   ` Eli Zaretskii
2013-05-04 12:45                                     ` martin rudalics
2013-05-04 13:18                                       ` Eli Zaretskii
2013-05-04 18:59                                         ` martin rudalics
2013-05-04 14:38                                 ` Drew Adams
2013-03-27 13:37   ` Drew Adams

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=83obdf69yz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14062@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=rudalics@gmx.at \
    /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).