From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 13743@debbugs.gnu.org
Subject: bug#13743: 24.2.93; Segmentation fault when trying to [s]teal a file opened elsewhere
Date: Tue, 26 Feb 2013 20:42:39 +0200 [thread overview]
Message-ID: <831uc2j4rk.fsf@gnu.org> (raw)
In-Reply-To: <512C3328.4070103@yandex.ru>
> Date: Tue, 26 Feb 2013 07:59:36 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: monnier@iro.umontreal.ca, 13743@debbugs.gnu.org
>
> On 26.02.2013 7:51, Eli Zaretskii wrote:
> >> Date: Tue, 26 Feb 2013 03:23:11 +0400
> >> From: Dmitry Gutov <dgutov@yandex.ru>
> >> CC: monnier@iro.umontreal.ca, 13743@debbugs.gnu.org
> >>
> >> On 25.02.2013 23:31, Eli Zaretskii wrote:
> >>>> Date: Mon, 25 Feb 2013 23:08:04 +0400
> >>>> From: Dmitry Gutov <dgutov@yandex.ru>
> >>>> CC: monnier@iro.umontreal.ca, 13743@debbugs.gnu.org
> >>>>
> >>>> On 25.02.2013 20:27, Eli Zaretskii wrote:
> >>>>> Btw, what mmm-mode does is quite nasty, because it causes stale lock
> >>>>> files to be left behind, if you press 'p' when Emacs says that the
> >>>>> file is locked. This is because mmm-mode makes the buffer unmodified
> >>>>> again after doing whatever it is that causes these prompts, and if you
> >>>>> then kill Emacs without ever editing the file, the function that
> >>>>> unlocks the file is not called (because the buffer is not modified).
> >>>>
> >>>> AFAICT, it only did that to make sure the subsequent `kill-buffer'
> >>>> doesn't query the user. It doesn't seem to do that either way, so I
> >>>> removed the `set-buffer-modified-p' call.
> >>>
> >>> And after removing that call, do you end up with a "modified" buffer
> >>> after visiting a file?
> >>
> >> Nope.
> >
> > Then the root cause is still there: the file is locked by an operation
> > that leaves the buffer unmodified.
>
> Any ideas what that might be? mmm-mode initialization code is rather
> complex.
I suggest to run Emacs under GDB, put a breakpoint in lock_file and
unlock_file, and when they break, see who calls them in C and in Lisp.
next prev parent reply other threads:[~2013-02-26 18:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 6:41 bug#13743: 24.2.93; Segmentation fault when trying to [s]teal a file opened elsewhere Dmitry Gutov
2013-02-18 16:11 ` Eli Zaretskii
2013-02-19 0:52 ` Dmitry Gutov
2013-02-20 19:31 ` Eli Zaretskii
2013-02-21 8:30 ` Dmitry Gutov
2013-02-18 19:35 ` Glenn Morris
2013-02-19 0:55 ` Dmitry Gutov
2013-02-21 5:16 ` Paul Eggert
2013-02-21 7:03 ` Dmitry Gutov
2013-02-23 3:37 ` Dmitry Gutov
2013-02-23 15:10 ` Eli Zaretskii
2013-02-23 16:59 ` Stefan Monnier
2013-02-23 18:44 ` Eli Zaretskii
2013-02-24 15:28 ` Dmitry Gutov
2013-02-24 15:50 ` Eli Zaretskii
2013-02-25 5:52 ` Dmitry Gutov
2013-02-25 15:25 ` Stefan Monnier
2013-02-25 16:37 ` Eli Zaretskii
2013-02-25 18:29 ` Stefan Monnier
2013-02-25 18:56 ` Eli Zaretskii
2013-02-25 20:28 ` Stefan Monnier
2013-02-26 3:39 ` Eli Zaretskii
2013-02-26 4:35 ` Stefan Monnier
2013-03-02 9:30 ` Eli Zaretskii
2013-02-25 16:25 ` Eli Zaretskii
2013-02-25 18:27 ` Dmitry Gutov
2013-02-25 16:27 ` Eli Zaretskii
2013-02-25 19:08 ` Dmitry Gutov
2013-02-25 19:31 ` Eli Zaretskii
2013-02-25 23:23 ` Dmitry Gutov
2013-02-26 3:51 ` Eli Zaretskii
2013-02-26 3:59 ` Dmitry Gutov
2013-02-26 18:42 ` Eli Zaretskii [this message]
2013-02-27 17:46 ` Dmitry Gutov
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=831uc2j4rk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13743@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.