unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
@ 2013-12-17  2:39 Drew Adams
  2014-02-10  3:55 ` Lars Ingebrigtsen
  2019-08-08  4:15 ` Stefan Kangas
  0 siblings, 2 replies; 9+ messages in thread
From: Drew Adams @ 2013-12-17  2:39 UTC (permalink / raw)
  To: 16172

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@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'





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2013-12-17  2:39 bug#16172: 24.3.50; C-g in minibuffer hangs Emacs Drew Adams
@ 2014-02-10  3:55 ` Lars Ingebrigtsen
  2014-02-10 22:25   ` Drew Adams
  2019-08-08  4:15 ` Stefan Kangas
  1 sibling, 1 reply; 9+ messages in thread
From: Lars Ingebrigtsen @ 2014-02-10  3:55 UTC (permalink / raw)
  To: Drew Adams; +Cc: 16172

Drew Adams <drew.adams@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/





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2014-02-10  3:55 ` Lars Ingebrigtsen
@ 2014-02-10 22:25   ` Drew Adams
  2016-04-29 14:50     ` Lars Ingebrigtsen
  0 siblings, 1 reply; 9+ messages in thread
From: Drew Adams @ 2014-02-10 22:25 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 16172

> > 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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2014-02-10 22:25   ` Drew Adams
@ 2016-04-29 14:50     ` Lars Ingebrigtsen
  0 siblings, 0 replies; 9+ messages in thread
From: Lars Ingebrigtsen @ 2016-04-29 14:50 UTC (permalink / raw)
  To: Drew Adams; +Cc: 16172

Drew Adams <drew.adams@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





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2013-12-17  2:39 bug#16172: 24.3.50; C-g in minibuffer hangs Emacs Drew Adams
  2014-02-10  3:55 ` Lars Ingebrigtsen
@ 2019-08-08  4:15 ` Stefan Kangas
  2019-08-08 15:27   ` Drew Adams
  1 sibling, 1 reply; 9+ messages in thread
From: Stefan Kangas @ 2019-08-08  4:15 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 16172

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Drew Adams <drew.adams@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





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2019-08-08  4:15 ` Stefan Kangas
@ 2019-08-08 15:27   ` Drew Adams
  2019-10-29 23:21     ` Lars Ingebrigtsen
  0 siblings, 1 reply; 9+ messages in thread
From: Drew Adams @ 2019-08-08 15:27 UTC (permalink / raw)
  To: Stefan Kangas, Lars Ingebrigtsen; +Cc: 16172

 
> 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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2019-08-08 15:27   ` Drew Adams
@ 2019-10-29 23:21     ` Lars Ingebrigtsen
  2019-10-29 23:35       ` Drew Adams
  0 siblings, 1 reply; 9+ messages in thread
From: Lars Ingebrigtsen @ 2019-10-29 23:21 UTC (permalink / raw)
  To: Drew Adams; +Cc: 16172, Stefan Kangas

Drew Adams <drew.adams@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





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2019-10-29 23:21     ` Lars Ingebrigtsen
@ 2019-10-29 23:35       ` Drew Adams
  2019-10-30 11:02         ` Lars Ingebrigtsen
  0 siblings, 1 reply; 9+ messages in thread
From: Drew Adams @ 2019-10-29 23:35 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 16172, Stefan Kangas

> 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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#16172: 24.3.50; C-g in minibuffer hangs Emacs
  2019-10-29 23:35       ` Drew Adams
@ 2019-10-30 11:02         ` Lars Ingebrigtsen
  0 siblings, 0 replies; 9+ messages in thread
From: Lars Ingebrigtsen @ 2019-10-30 11:02 UTC (permalink / raw)
  To: Drew Adams; +Cc: 16172, Stefan Kangas

Drew Adams <drew.adams@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





^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2019-10-30 11:02 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-17  2:39 bug#16172: 24.3.50; C-g in minibuffer hangs Emacs Drew Adams
2014-02-10  3:55 ` Lars Ingebrigtsen
2014-02-10 22:25   ` Drew Adams
2016-04-29 14:50     ` Lars Ingebrigtsen
2019-08-08  4:15 ` Stefan Kangas
2019-08-08 15:27   ` Drew Adams
2019-10-29 23:21     ` Lars Ingebrigtsen
2019-10-29 23:35       ` Drew Adams
2019-10-30 11:02         ` Lars Ingebrigtsen

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).