Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
emacs-helm
Home
+ new post
About this group
Join this group
Message from discussion Crash on Windows
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Thierry Volpiatto  
View profile  
 More options Aug 2 2012, 1:35 pm
From: Thierry Volpiatto <thierry.volpia...@gmail.com>
Date: Thu, 02 Aug 2012 19:35:46 +0200
Local: Thurs, Aug 2 2012 1:35 pm
Subject: Re: Crash on Windows
Print | View thread | Show original | Report this message | Find messages by this author
Hi Sebastien,

"Sebastien Vauban" <wxhgmqzgw...@spammotel.com> writes:
> Hi Thierry,

> Remember that Anything (at that time) crashed on Windows -- 6 months ago or so
> --, and that you changed some code, making "Emacs" behave correctly after
> that?

> Well, I did yesterday an update of Helm (last one was from June or so), and
> similar problems come back to light.

> Some details:

>     GNU Emacs 24.1.1 (i386-mingw-nt5.1.2600) of 2012-06-02 on MARVIN
>     on Windows XP

> The only helm-commands I'm using:

> - <f3> runs the command helm-for-files
> - M-x runs the command helm-M-x

> The problems (which reappared from yesterday) were noticed when using
> `helm-for-files'. I enter some letters to identify the file or buffer I'm
> after, and Emacs simply blocks. Doing `C-g' has no effect at all. Waiting
> neither. The only exit I have is killing Emacs and restarting a new one.

> Once again, I don't say that (the new version of) Helm is the culprit, but
> somehow the interactions between Helm and Everything (and the Cygwin shell
> maybe) make Emacs block at some point.

I tried hard right now to make Emacs crashing with helm but couldn't,
can't reproduce your crash either from Linux and Windows.

Did you try from emacs -Q?

Can you run Emacs inside gdb? (This is the only way to debug
efficiently).

Also you could send a bug report to Emacs, like this people at Emacs can
try to reproduce inside gdb from the build directory.

> Temporarily, I've checked out an older version of Helm, and will try to bisect
> until I fond the problematic one, but that'll take some time...

>     commit 35fc048e36f20e605285eded155cc6b63f1c3b04
>     Author: Michael Markert <markert.mich...@googlemail.com>
>     Date:   Wed Jun 6 21:35:18 2012 +0200

> For your information, the "Emacs is blocked" rate is something like 4 times a
> day, on Helm yesterday's version.

> Best regards,
>   Seb

--
  Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google