[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#14062: 24.3.50; emacs_backtrace.txt
From: |
martin rudalics |
Subject: |
bug#14062: 24.3.50; emacs_backtrace.txt |
Date: |
Mon, 15 Apr 2013 21:22:00 +0200 |
> But for nil, BUFFERP will return zero, and the code that uses XBUFFER
> should not be called, IMO.
[...]
> But the uninitialized contents field should be zero, no? Again, it
> should not pass the BUFFERP test.
>
> So the mystery still stands.
You mean that the w->contents argument of XBUFFER _always_ passes the
BUFFERP test first and then fails at the assertion in XBUFFER? How can
that make sense?
martin
- bug#14062: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt, Juanma Barranquero, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt, martin rudalics, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt, martin rudalics, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2013/04/15
- bug#14062: 24.3.50; emacs_backtrace.txt,
martin rudalics <=
- bug#14062: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2013/04/16
- bug#14062: 24.3.50; emacs_backtrace.txt, Drew Adams, 2013/04/22
- bug#14062: 24.3.50; emacs_backtrace.txt, Juanma Barranquero, 2013/04/22
- bug#14062: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2013/04/22
- bug#14062: 24.3.50; emacs_backtrace.txt, Drew Adams, 2013/04/22