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:54:16 +0100 [thread overview]
Message-ID: <53A44B18.3040202@cornell.edu> (raw)
In-Reply-To: <83r42jr63a.fsf@gnu.org>
On 6/20/2014 3:47 PM, Eli Zaretskii wrote:
>> Date: Fri, 20 Jun 2014 15:40:28 +0100
>> From: Ken Brown <kbrown@cornell.edu>
>> CC: 17817@debbugs.gnu.org
>>
>> (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.
>
> Yeah. But still, the machine insists the value was bad. Hmmm...
>
> Can you show the disassembly of bidi_check_type?
(gdb) disas bidi_check_type
Dump of assembler code for function bidi_check_type:
0x004d2837 <+0>: push %ebp
0x004d2838 <+1>: mov %esp,%ebp
0x004d283a <+3>: sub $0x18,%esp
0x004d283d <+6>: movzbl 0x9063f8,%eax
0x004d2844 <+13>: xor $0x1,%eax
0x004d2847 <+16>: test %al,%al
0x004d2849 <+18>: je 0x4d286d <bidi_check_type+54>
0x004d284b <+20>: cmpl $0x17,0x8(%ebp)
0x004d284f <+24>: jbe 0x4d286d <bidi_check_type+54>
0x004d2851 <+26>: movl $0x149,0x8(%esp)
0x004d2859 <+34>: movl $0x86cc70,0x4(%esp)
0x004d2861 <+42>: movl $0x86ccbc,(%esp)
0x004d2868 <+49>: call 0x56e818 <die>
0x004d286d <+54>: leave
0x004d286e <+55>: ret
End of assembler dump.
next prev parent reply other threads:[~2014-06-20 14:54 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
2014-06-20 14:47 ` Eli Zaretskii
2014-06-20 14:54 ` Ken Brown [this message]
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=53A44B18.3040202@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.