GNU bug report logs -
#16172
24.3.50; C-g in minibuffer hangs Emacs
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Tue, 17 Dec 2013 02:40:01 UTC
Severity: normal
Tags: moreinfo, unreproducible
Found in version 24.3.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16172 in the body.
You can then email your comments to 16172 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Tue, 17 Dec 2013 02:40:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org.
(Tue, 17 Dec 2013 02:40:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
No info to repro this yet. But now Emacs is sometimes hanging when I
try to interrupt the current command, which is using the minibuffer,
using C-g (or C-], after C-g at least) repeatedly. Doesn't seem to
happen all the time, but fairly often. The Task Manager does NOT
show Emacs gobbling CPU, which surprised me. But there seems to
be no way to exit Emacs besides killing the process.
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-12-14 on ODIEONE
Bzr revision: 115521 rudalics <at> gmx.at-20131214110600-euy4wbseyg78zh72
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Mon, 10 Feb 2014 03:57:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 16172 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
> No info to repro this yet. But now Emacs is sometimes hanging when I
> try to interrupt the current command, which is using the minibuffer,
> using C-g (or C-], after C-g at least) repeatedly. Doesn't seem to
> happen all the time, but fairly often. The Task Manager does NOT
> show Emacs gobbling CPU, which surprised me. But there seems to
> be no way to exit Emacs besides killing the process.
Works for me.
Are you still seeing this problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Added tag(s) unreproducible.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org.
(Mon, 10 Feb 2014 03:57:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Mon, 10 Feb 2014 22:26:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 16172 <at> debbugs.gnu.org (full text, mbox):
> > No info to repro this yet. But now Emacs is sometimes hanging
> > when I try to interrupt the current command, which is using the
> > minibuffer, using C-g (or C-], after C-g at least) repeatedly.
> > Doesn't seem to happen all the time, but fairly often. The Task
> > Manager does NOT show Emacs gobbling CPU, which surprised me.
> > But there seems to be no way to exit Emacs besides killing the
> > process.
>
> Works for me.
Really? What is it, exactly, that works for you? How do you know
it works?
> Are you still seeing this problem?
Yes, "sometimes", as I said in the bug report.
Removed tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org.
(Sat, 26 Dec 2015 01:37:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Fri, 29 Apr 2016 14:51:01 GMT)
Full text and
rfc822 format available.
Message #18 received at 16172 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
>> > No info to repro this yet. But now Emacs is sometimes hanging
>> > when I try to interrupt the current command, which is using the
>> > minibuffer, using C-g (or C-], after C-g at least) repeatedly.
>> > Doesn't seem to happen all the time, but fairly often. The Task
>> > Manager does NOT show Emacs gobbling CPU, which surprised me.
>> > But there seems to be no way to exit Emacs besides killing the
>> > process.
>>
>> Works for me.
>
> Really? What is it, exactly, that works for you? How do you know
> it works?
I did what you described. I used the minibuffer and interrupted the
command.
>> Are you still seeing this problem?
>
> Yes, "sometimes", as I said in the bug report.
Do you have a recipe for reproducing this bug?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org.
(Fri, 29 Apr 2016 14:51:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Thu, 08 Aug 2019 04:17:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 16172 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Drew Adams <drew.adams <at> oracle.com> writes:
>
>>> > No info to repro this yet. But now Emacs is sometimes hanging
>>> > when I try to interrupt the current command, which is using the
>>> > minibuffer, using C-g (or C-], after C-g at least) repeatedly.
>>> > Doesn't seem to happen all the time, but fairly often. The Task
>>> > Manager does NOT show Emacs gobbling CPU, which surprised me.
>>> > But there seems to be no way to exit Emacs besides killing the
>>> > process.
>>>
>>> Works for me.
>>
>> Really? What is it, exactly, that works for you? How do you know
>> it works?
>
> I did what you described. I used the minibuffer and interrupted the
> command.
>
>>> Are you still seeing this problem?
>>
>> Yes, "sometimes", as I said in the bug report.
>
> Do you have a recipe for reproducing this bug?
That was three years ago, and the message before that was five
years ago.
Are you still seeing this? Do you have a recipe for reproducing the
bug? Or could you provide a backtrace, or something that is a bit more
actionable than the original report from 2013?
Thanks,
Stefan Kangas
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Thu, 08 Aug 2019 15:28:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 16172 <at> debbugs.gnu.org (full text, mbox):
> That was three years ago, and the message before that was five
> years ago.
>
> Are you still seeing this? Do you have a recipe for reproducing the
> bug? Or could you provide a backtrace, or something that is a bit more
> actionable than the original report from 2013?
Yes, sometimes, as mentioned in the bug thread.
No, I don't have a recipe to repro it. Sorry.
And there is no backtrace - Emacs hangs.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Tue, 29 Oct 2019 23:22:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 16172 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
>> That was three years ago, and the message before that was five
>> years ago.
>>
>> Are you still seeing this? Do you have a recipe for reproducing the
>> bug? Or could you provide a backtrace, or something that is a bit more
>> actionable than the original report from 2013?
>
> Yes, sometimes, as mentioned in the bug thread.
> No, I don't have a recipe to repro it. Sorry.
> And there is no backtrace - Emacs hangs.
Could you try running Emacs under gdb and break when this happens so
that we can see where it hangs?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Tue, 29 Oct 2019 23:36:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 16172 <at> debbugs.gnu.org (full text, mbox):
> Could you try running Emacs under gdb and break when this happens so
> that we can see where it hangs?
No, sorry. I gave up on trying to use gdb long ago.
If you feel like closing the bug as `cannot reproduce'
or whatever, feel free to do so. I don't have time
to spend on it. Sorry.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#16172; Package
emacs.
(Wed, 30 Oct 2019 11:03:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 16172 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
>> Could you try running Emacs under gdb and break when this happens so
>> that we can see where it hangs?
>
> No, sorry. I gave up on trying to use gdb long ago.
> If you feel like closing the bug as `cannot reproduce'
> or whatever, feel free to do so. I don't have time
> to spend on it. Sorry.
It doesn't seem likely that we'll make further progress on this bug
report, so I'm closing it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
16172 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org.
(Wed, 30 Oct 2019 11:03:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Wed, 27 Nov 2019 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 202 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.