[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: List of some current problems
From: |
Stefan Monnier |
Subject: |
Re: List of some current problems |
Date: |
Tue, 22 Jul 2003 14:28:55 -0400 |
> 1. I can confirm the recent report
>
> <URL:http://mail.gnu.org/archive/html/emacs-devel/2003-07/msg00318.html>
>
> This bug causes my Solaris machine to beep forever like with
> (while t (ding)). I found no way to stop this except to reboot
> the machine. I can't even login from another machine to kill the
> Emacs process.
>
> I had experienced this problem under other scenarios as well. I
> don't remember when this occured first, but it was not very long
> ago. In one case show-paren-mode was turned on and I used
> query-replace-regexp.
I think I've fixed this one, please tell me if it occurs again.
> 2. Same problem when actually evaluating (while t (ding)). No way to
> stop the beeb except rebooting.
Can't reproduce that with `emacs -q --no-site-file' and
M-: (while t (ding)) RET on my GNU/Linux machine.
It's probably platform dependent.
> 3. CVS Emacs crashes frequently. So often that I usually use the
> stable 21.3 version. The backtraces from gdb look similar to the
> one reported in
>
>
> <URL:http://mail.gnu.org/archive/html/emacs-pretest-bug/2003-02/msg00118.html>
When did this start happening ? Does it date back to February ?
Can you try and recompile with -DGC_CHECK_MARKED_OBJECTS ?
Also what do you mean by "look similar" ?
Can you show us a few of your backtraces and try give us an idea
of what you'd done before Emacs crashed ?
> 4. The file-name completion problem reported on emacs-pretesters
>
> From: "Marshall, Simon" <address@hidden>
> To: "'Emacs Pretesters'" <address@hidden>
> Subject: Anyone seen a barf on TAB in minibuffer when a valid
> completion exists?
> Date: Thu, 16 Jan 2003 12:15:04 -0000
Could somneone resend it to a more appropriate place ?
> 5. The redisplay problem reported on
>
>
> <URL:http://mail.gnu.org/archive/html/emacs-pretest-bug/2003-06/msg00166.html>
>
> still exists.
Yes, I also see it sometimes. But I don't know how to debug it and
I can't reproduce it on demand. Have you found a recipe to reproduce
the problem ?
Stefan