From: Eli Zaretskii <eliz@gnu.org>
To: rudalics@gmx.at
Cc: yfb02119@nifty.com, 13262@debbugs.gnu.org
Subject: bug#13262: 24.3.50; crash when multibyte directory name completion.
Date: Mon, 24 Dec 2012 23:26:56 +0200 [thread overview]
Message-ID: <83sj6vnntr.fsf@gnu.org> (raw)
In-Reply-To: <83txrbno4o.fsf@gnu.org>
> Date: Mon, 24 Dec 2012 23:20:23 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: yfb02119@nifty.com, 13262@debbugs.gnu.org
>
> > Date: Mon, 24 Dec 2012 19:21:10 +0100
> > From: martin rudalics <rudalics@gmx.at>
> >
> > > Sorry, the changes touch quite a few places, but they all had the same
> > > problem: unwarranted assumptions that input Lisp strings passed to
> > > primitives are multibyte. The crash happened because file completion
> > > calls directory-file-name with a unibyte string (an encoded file
> > > name). A similar mess was found and fixed in file-name-directory and
> > > in expand-file-name.
> >
> > There's a crash I can reproduce easily but only randomly with my setup
> > and not with emacs -Q (backtrace with actual trunk). Can it be related?
>
> No. The changes were all made in functions that manipulate file
> names, not something even remotely related to redisplay.
>
> Any chance of a recipe? Also, what data causes the crash?
Better file a new bug report, btw.
Also, does this buffer position make sense?
Program received signal SIGSEGV, Segmentation fault.
0x0107160b in FETCH_MULTIBYTE_CHAR (pos=54295370) at buffer.h:1168
^^^^^^^^^^^^
Were you indeed editing a 54MB buffer?
next prev parent reply other threads:[~2012-12-24 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 1:25 bug#13262: 24.3.50; crash when multibyte directory name completion yfb02119
2012-12-24 5:10 ` Stefan Monnier
2012-12-24 16:21 ` Eli Zaretskii
2012-12-24 18:21 ` martin rudalics
2012-12-24 21:20 ` Eli Zaretskii
2012-12-24 21:26 ` Eli Zaretskii [this message]
2012-12-25 18:08 ` martin rudalics
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=83sj6vnntr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13262@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=yfb02119@nifty.com \
/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.