From: Noam Postavsky <npostavs@users.sourceforge.net>
To: 22178@debbugs.gnu.org
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#22178: Bug #22178: 25: segfault from insert-buffer-contents
Date: Sun, 26 Jun 2016 22:14:46 -0400 [thread overview]
Message-ID: <CAM-tV-_E_zhwhyVk6LFg=8STipKrmm4ivwCw2pzstWoyZ4jakQ@mail.gmail.com> (raw)
In-Reply-To: <CAHZoxq-jDbXfeL6Rgs3j6xBV3MUbs-kvMFmzCmRU3JEoYMsw5w@mail.gmail.com>
> I think I had just done M-x dired.
Yeah, I can see the dired call in your stacktrace, I guess this has to
do with the particular contents of that directory. Can you reproduce
this, or was it a one-off?
next prev parent reply other threads:[~2016-06-27 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 15:20 bug#22178: 25: segfault from insert-buffer-contents Eric Hanchrow
2016-06-27 2:14 ` Noam Postavsky [this message]
2016-06-27 2:35 ` bug#22178: Bug #22178: " Eric Hanchrow
2016-06-27 2:37 ` Noam Postavsky
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='CAM-tV-_E_zhwhyVk6LFg=8STipKrmm4ivwCw2pzstWoyZ4jakQ@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=22178@debbugs.gnu.org \
--cc=eric.hanchrow@gmail.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 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).