Tassilo Horn | 2 Jul 11:07 2007
Face

(recentf-mode 1) aborts emacs


Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Hi,

since I updated my emacs checkout (head, not a branch) this morning my
emacs shuts down immediately after starting. This was due to a SIGABRT. I
commented out things in my ~/.emacs and found out that the line
(recentf-mode 1) causes this bug.

I made a backtrace with a ~/.emacs only containing the line

  (recentf-mode 1)

and did `gdb --args /usr/bin/emacs-22-cvs -Q -l .emacs'. The backtrace
is pasted here: http://paste.lisp.org/display/43790

The checkout I compiled yesterday morning (CEST) worked just fine.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/22.1.50/etc/DEBUG for instructions.
(Continue reading)

Tassilo Horn | 2 Jul 20:50 2007
Face
Picon

Emacs crashes with SIGABRT (was: (recentf-mode 1) aborts emacs)

Hi all,

I just wanted to mention that this bug seems not to be strictly related
to (recentf-mode 1), but that triggers the bug immediately. But although
I commented out this line (and all of recentf settings), emacs crashed
with SIGABRT after about 10 hours uptime. Unfortunately it didn't run in
the debugger this time...

My observations are that the bug occurs much more often when I run emacs
with its GTK interface than the terminal version.

Bye,
Tassilo
Reiner Steib | 2 Jul 21:07 2007
X-Face

Re: A bug in doc string of `gnus-level-unsubscribed'?

On Mon, Jun 11 2007, Leo wrote:

>> Is the following doc string more clear?
>>
>> ,----[ <f1> v gnus-level-unsubscribed RET ]
>> | gnus-level-unsubscribed is a variable defined in `gnus-start.el'.
>> | Its value is 7
>> | 
>> | 
>> | Documentation:
>> | Groups with levels less than or equal to this variable are
>> | unsubscribed. 
>
> This sentence looks redundant to me. The rest is clear.

The first sentence should fit in 80 columns including "  Variable: "
prepended.  So I tried to find a useful first line.  Does anyone have
a better suggestion?

>> | Groups with levels less than `gnus-level-subscribed', which should
>> | be less than this variable, are subscribed.  Groups with levels from
>> | `gnus-level-subscribed' (exclusive) upto this variable (inclusive)
>> | are unsubscribed.  See also `gnus-level-zombie', `gnus-level-killed'
>> | and the Info node `Group Levels' for details.
>> `----

Bye, Reiner.
--

-- 
       ,,,
      (o o)
(Continue reading)

Tassilo Horn | 2 Jul 21:30 2007
Picon

Re: Emacs crashes with SIGABRT

Hi all,

I updated again and ran emacs in gdb. Here are three backtraces. The first is
with emacs using its GTK interface, the last two happened when emacs ran in a
terminal.

Backtrace 1:
============

heimdall <at> baldur ~> gdb /usr/bin/emacs-22-cvs
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/emacs-22-cvs
[Thread debugging using libthread_db enabled]
[New Thread -1220736448 (LWP 21813)]
_IceTransOpen: Unable to Parse address

Program received signal SIGABRT, Aborted.
[Switching to Thread -1220736448 (LWP 21813)]
0xb7faf410 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7faf410 in __kernel_vsyscall ()
#1  0xb757a476 in kill () from /lib/libc.so.6
(Continue reading)

Явор Доганов | 3 Jul 09:40 2007
Picon

Byte-compilation of po-mode.el fails


With CVS trunk as of yesterday, Emacs fails when byte-compiling
po-mode.el from gettext 0.14.5 (same with 0.16.1).  This doesn't
happen with a snapshot from 25 Jun.  I haven't investigated further.

In po-ediff-buffers-exit-recursive:
po-mode.el:2045:30:Warning: `insert-buffer' used from Lisp code
That command is designed for interactive use only
po-mode.el:2048:19:Warning: reference to free variable `entry-buffer'

In po-send-mail:
po-mode.el:3252:40:Warning: `insert-buffer' used from Lisp code
That command is designed for interactive use only
po-mode.el:3258:4:Error: Symbol's value as variable is void: TAG

In GNU Emacs 22.1.50.1 (i486-pc-linux-gnu)
 of 2007-07-02 on tzotzolana, modified for gNewSense
 (Unofficial gNewSense emacs-snapshot package, version 1:20070702-gns1)
Yavor Doganov | 3 Jul 11:24 2007
Picon

Re: Byte-compilation of po-mode.el fails

After reverting this change

2007-07-01  Paul Pogonyshev  <pogonyshev <at> gmx.net>

	* emacs-lisp/byte-opt.el: Set `binding-is-magic'
	property on a few symbols.
	(byte-compile-side-effect-free-dynamically-safe-ops): New defconst.
	(byte-optimize-lapcode): Remove bindings that are not referenced
	and certainly will not effect through dynamic scoping.

I don't experience the problem.
Zhang Wei | 4 Jul 15:56 2007
Picon

Info pages opened with an incorrect coding system

When I enter Info, the info doc is allways opened with chinese-iso-8bit
coding system which is the default of my installation. If there are
non-ascii characters in the doc, it will be displayed incorrectly, such
as the emacs-mime page, there's a word `Naïve' in the page, and it
should be opened with iso-8859-1.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Emacs/etc/DEBUG for instructions.

In GNU Emacs 22.1.50.1 (i386-mingw-nt5.1.2600)
 of 2007-06-23 on BREP
modified by Zhangwei <id.brep <at> gmail.com>.
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.2)'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: CHS
  locale-coding-system: cp936
  default-enable-multibyte-characters: t

(Continue reading)

Eli Zaretskii | 4 Jul 23:37 2007
Picon

Re: Info pages opened with an incorrect coding system

> From: Zhang Wei <id.brep <at> gmail.com>
> Date: Wed, 04 Jul 2007 21:56:40 +0800
> 
> When I enter Info, the info doc is allways opened with chinese-iso-8bit
> coding system which is the default of my installation.

Thank you for reporting this.  Unfortunately, I seem to be unable to
reproduce this on my XP machine.

Does the problem happen with "emacs -Q"?  If it doesn't, then
something in your .emacs init file causes this.
Katsumi Yamaoka | 5 Jul 03:03 2007
X-Face

texinfmt crashes Emacs

Hi,

I noticed the recent change in texinfmt.el crashes Emacs when
formatting a Japanese Info.  The Lisp program that reproduces
the crash is:

(load-file "infohack.el")
(let (enable-local-variables) (infohack-texi-format "gnus-ja.texi"))

Where infohack.el, gnus-ja.texi and the other requirements are in:

http://cvs.m17n.org/viewcvs/root/gnus-doc-ja.tar.gz?view=tar
or
http://www.jpl.org/gnus-doc-ja/ngnus-0.6-doc-ja.tar.gz

The backtrace is below.

In GNU Emacs 22.1.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2007-07-05 on pastis
Windowing system distributor `The X.Org Foundation', version 11.0.10300000
configured using `configure  '--verbose' '--with-x-toolkit=lucid'\
 '--with-gpm' '--without-xim''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: C
  value of $LC_CTYPE: ja_JP.eucjp
  value of $LC_MESSAGES: C
  value of $LC_MONETARY: C
  value of $LC_NUMERIC: C
(Continue reading)

Richard Stallman | 5 Jul 03:31 2007
Picon
Picon

Re: Info pages opened with an incorrect coding system

    When I enter Info, the info doc is allways opened with chinese-iso-8bit
    coding system which is the default of my installation. If there are
    non-ascii characters in the doc, it will be displayed incorrectly, such
    as the emacs-mime page, there's a word `Naïve' in the page, and it
    should be opened with iso-8859-1.

Since this depends on something unusual about your system,
most of us cannot easily investigate it.
Can you please investigate how this happens?

I have cc'd Handa-san, whose area this is in.

Please report back about whatever progress you can make.

Gmane