From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: david.reitter@gmail.com, 15765@debbugs.gnu.org
Subject: bug#15765: Crash in directory_files_internal
Date: Mon, 29 Feb 2016 17:40:36 +0200 [thread overview]
Message-ID: <83wppn8qyz.fsf@gnu.org> (raw)
In-Reply-To: <878u24uljb.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 29 Feb 2016 16:34:48 +1100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 29 Feb 2016 16:34:48 +1100
> Cc: 15765@debbugs.gnu.org
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > David Reitter <david.reitter@gmail.com> writes:
> >
> >> This crash occurred after eval'ing the expression
> >>
> >> (directory-files "~/Library/Logs/DiagnosticReports" t "Aquamacs.*.crash")
> >>
> >> This directory exists, contains a few files, and I had eval'ed that
> >> just a few second earlier without problems.
> >>
> >> The bug does not reproduce.
> >>
> >> Relevant lines in my dired.c:
> >>
> >>> 267 Lisp_Object fullname;
> >>> 268 ptrdiff_t nbytes = len + directory_nbytes + needsep;
> >>> 269 ptrdiff_t nchars;
> >>>
> >>> 271 fullname = make_uninit_multibyte_string (nbytes, nbytes);
> >>> 272 memcpy (SDATA (fullname), SDATA (directory),
> >>> directory_nbytes);
> >>>
> >>
> >> Full crash log below. The running binary was built based on Emacs
> >> head as per Oct 24, git refid 7c5015698c3, with some patches, but
> >> none to dired.c.
> >
> > Have you seen this again later?
>
> More information was requested, but no response was given within a few
> months, so I'm closing this bug report. If the problem still exists,
> please reopen this bug report.
It's entirely possible that this was due to the problem with decoding
file names on OS X HFS+ filesystems and treating their decomposed form
correctly, something solved a few months ago.
prev parent reply other threads:[~2016-02-29 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 22:06 bug#15765: Crash in directory_files_internal David Reitter
2015-12-26 1:12 ` Lars Ingebrigtsen
2016-02-29 5:34 ` Lars Ingebrigtsen
2016-02-29 15:40 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wppn8qyz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15765@debbugs.gnu.org \
--cc=david.reitter@gmail.com \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).