From: Michael Albinus <michael.albinus@gmx.de>
To: felix.dick@web.de
Cc: 25170@debbugs.gnu.org
Subject: bug#25170: 26.0.50; emacs crashes on using tramp
Date: Sun, 11 Dec 2016 14:28:04 +0100 [thread overview]
Message-ID: <87shpua93v.fsf@gmx.de> (raw)
In-Reply-To: <874m2alkpv.fsf@desktop.i-did-not-set--mail-host-address--so-tickle-me> (felix dick's message of "Sun, 11 Dec 2016 13:21:48 +0100")
felix.dick@web.de writes:
Hi Felix,
> At first, i have to say that i'm sorry that I dont use the proper report-emacs-bug system, but I didn't succeed doing that.
> It's really not easy to use this emacs bug-reporting system, and if you want everybody to be able to report bugs, the system should be simpler!
Could you pls tell us in detail what annoys you?
> Anyways, here is the Bug report, if I follow this, emacs crashes every time.
> I use arch linux x86-64
> If i start 'emacs -Q'
> after 'C-x C-f' (find-file) and entering '/ssh:'
For the records, this doesn't happen for me with a todays build of git
master:
GNU Emacs 26.0.50.17 (x86_64-pc-linux-gnu, GTK+ Version 2.24.30)
of 2016-12-11
I'm running Ubuntu 16.10.
> in the moment I type the colon, emacs crashes with the backtrace:
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x493d25]
> emacs[0x530a17]
> emacs[0x48931e]
> emacs[0x44ba43]
> /usr/lib/libpthread.so.0(+0x11080)[0x7f57f777f080]
Looks like a problem in the concurrency code. Could you, pls, check the
instructions in etc/DEBUG how to retrieve better traces?
Thanks, and best regards, Michael.
next prev parent reply other threads:[~2016-12-11 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 12:21 bug#25170: 26.0.50; emacs crashes on using tramp felix.dick
2016-12-11 13:28 ` Michael Albinus [this message]
2016-12-11 13:33 ` Felix
2017-12-11 12:27 ` Michael Albinus
2016-12-11 18:05 ` 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
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=87shpua93v.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=25170@debbugs.gnu.org \
--cc=felix.dick@web.de \
/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).