all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <amoreton@solarflare.com>
Cc: 17275@debbugs.gnu.org
Subject: bug#17275: emacs-24 crash in dired
Date: Wed, 16 Apr 2014 16:39:44 +0300	[thread overview]
Message-ID: <83eh0xjsv3.fsf@gnu.org> (raw)
In-Reply-To: <534E5A4E.7030703@solarflare.com>

> Date: Wed, 16 Apr 2014 11:24:14 +0100
> From: Andy Moreton <amoreton@solarflare.com>
> 
> Running emacs 24 on win7 64bit built from r116968 with mingw32 gcc 4.7.2.
> 
>  From "emacs -Q"
> 1) Open a dired buffer:
>     C-x C-f ~/.emacs.d RET
> 
> 2) Switch to external 'ls' program
>    (setq insert-directory-program "C:/cygwin/bin/ls.exe")
>    (setq ls-lisp-use-insert-directory-program t)
>    (setq dired-listing-switches "-al --group-directories-first")
> 
> 3) Type 'g' in the dired buffer (bound to revert-buffer)
>     Emacs shows the abort dialog.
> 
> This is a recent regression (within the last week) as I build emacs from 
> source daily. This bug does not manifest in current emacs trunk builds.

Sorry, I can't reproduce this here.  There's a slight chance that this
is because my ls.exe is not a Cygwin program, but I doubt that's the
cause.

(Anyway, why do you switch to ls.exe after you already have a Dired
buffer produced by ls-lisp.el?  Does the problem happen if you do the
switch before visiting the directory?)

>     I have not managed to get gdb to emit a usable backtrace.

Did you try starting Emacs under GDB in the first place?





  reply	other threads:[~2014-04-16 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 10:24 bug#17275: emacs-24 crash in dired Andy Moreton
2014-04-16 13:39 ` Eli Zaretskii [this message]
2014-04-16 16:08   ` Andy Moreton
2014-04-16 18:38     ` Eli Zaretskii
2014-04-16 22:06       ` Andy Moreton
2014-04-17  7:31         ` Eli Zaretskii
2014-04-17  9:51           ` Andy Moreton
2014-04-17 10:18             ` Eli Zaretskii

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=83eh0xjsv3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17275@debbugs.gnu.org \
    --cc=amoreton@solarflare.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.