From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17817@debbugs.gnu.org
Subject: bug#17817: 24.3.91; Assertion failure in bidi.c (Cygwin-w32 build)
Date: Fri, 20 Jun 2014 15:40:28 +0100 [thread overview]
Message-ID: <53A447DC.3000108@cornell.edu> (raw)
In-Reply-To: <83wqcbr79c.fsf@gnu.org>
On 6/20/2014 3:21 PM, Eli Zaretskii wrote:
>> Date: Fri, 20 Jun 2014 14:42:05 +0100
>> From: Ken Brown <kbrown@cornell.edu>
>>
>> I just got the following assertion failure:
>>
>> bidi.c:329: Emacs fatal error: assertion failed: UNKNOWN_BT <= type
>> && type <= NEUTRAL_ON
>
> Is this the same 64-bit Cygwin-w32 build that was reported lately to
> produce nonsensical backtraces?
Yes.
>> #0 terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:351
>> No locals.
>> #1 0x00000001005ba95d in die (
>> msg=0x100a2e538 <DEFAULT_REHASH_SIZE+64> "UNKNOWN_BT <= type && type <= NEUTRAL_ON", file=0x100a2e530 <DEFAULT_REHASH_SIZE+56> "bidi.c", line=329)
>> at alloc.c:6826
>> No locals.
>> #2 0x00000001004fb4fe in bidi_check_type (type=STRONG_L) at bidi.c:329
>> No locals.
>> #3 0x0000000100500630 in bidi_level_of_next_char (bidi_it=0x2267d8)
>> at bidi.c:2430
>> type = STRONG_L
>> level = 0
>> prev_level = 0
>> next_for_neutral = {
>> bytepos = 0,
>> charpos = -1,
>> type = UNKNOWN_BT,
>> type_after_w1 = UNKNOWN_BT,
>> orig_type = UNKNOWN_BT
>> }
>> next_char_pos = 1
>
> This makes no sense at all: STRONG_L is one of the bidi types defined
> by 'enum bidi_type_t' (see dispextern.h), and therefore its value
> _must_ be between UNKNOWN_BT (whose value is zero) and NEUTRAL_ON, the
> last tag in the enumeration type.
>
> Can you see the numerical value of 'type' in frame #2? Like this:
>
> (gdb) fr 2
> (gdb) p type + 0
> Also, using a similar technique, display the values of UNKNOWN_BT and
> of NEUTRAL_ON.
(gdb) p type + 0
$2 = 1
(gdb) p UNKNOWN_BT + 0
$3 = 0
(gdb) p NEUTRAL_ON + 0
$4 = 23
So, as you said, this is nonsense.
Ken
next prev parent reply other threads:[~2014-06-20 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 13:42 bug#17817: 24.3.91; Assertion failure in bidi.c (Cygwin-w32 build) Ken Brown
2014-06-20 14:21 ` Eli Zaretskii
2014-06-20 14:40 ` Ken Brown [this message]
2014-06-20 14:47 ` Eli Zaretskii
2014-06-20 14:54 ` Ken Brown
2014-06-20 16:43 ` Ken Brown
2014-06-20 18:29 ` Eli Zaretskii
2014-06-21 19:14 ` Ken Brown
2014-06-21 19:30 ` Eli Zaretskii
2014-06-21 19:36 ` Ken Brown
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=53A447DC.3000108@cornell.edu \
--to=kbrown@cornell.edu \
--cc=17817@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.