From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14264@debbugs.gnu.org, jim@meyering.net
Subject: bug#14264: 24.3.50; SEGV in char_table_ref's use of SUB_CHAR_TABLE_P
Date: Tue, 08 Jul 2014 13:53:00 -0400 [thread overview]
Message-ID: <jwvbnszspsj.fsf-monnier+bug#14264@gnu.org> (raw)
In-Reply-To: <83li1khreb.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Oct 2013 19:40:44 +0300")
>> > Sorry, still no cigar.
>> Any other info I can usefully provide?
> Well, it would be useful to find out how come Emacs comes with such a
> bogus character code in the middle of what is supposed to be pure
> ASCII text. Can you set a breakpoint in scan_for_column, just before
> it calls composition_compute_stop_pos, conditioned on scan = 1645,
> then step inside composition_compute_stop_pos, and see how come it
> fetches such a character code? Is buffer text being corrupted by
> something?
Any news on this?
I couldn't reproduce the bug right now, but I also couldn't find the
relevant article in my news server. Can someone still reproduce
this bug? If so, can he/she provide an updated recipe (maybe using a
public NNTP server, so it doesn't depend on which server one uses.
I guess the gmane server would be a good choice)?
Stefan
next prev parent reply other threads:[~2014-07-08 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 5:57 bug#14264: 24.3.50; SEGV in char_table_ref's use of SUB_CHAR_TABLE_P Jim Meyering
2013-04-25 16:18 ` Eli Zaretskii
2013-04-26 23:44 ` Jim Meyering
2013-10-21 23:23 ` Glenn Morris
2013-10-21 23:30 ` Glenn Morris
2013-10-22 16:51 ` Eli Zaretskii
2013-10-22 18:25 ` Glenn Morris
2013-10-22 20:30 ` Eli Zaretskii
2013-10-23 7:53 ` Glenn Morris
2013-10-23 16:40 ` Eli Zaretskii
2014-07-08 17:53 ` Stefan Monnier [this message]
2014-07-08 19:33 ` Eli Zaretskii
2014-07-08 19:42 ` Jim Meyering
2014-07-08 20:26 ` Jim Meyering
2014-07-08 20:25 ` Stefan Monnier
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='jwvbnszspsj.fsf-monnier+bug#14264@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=14264@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jim@meyering.net \
/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.