Gnus development mailing list
 help / color / mirror / Atom feed
From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org>
To: emacs-pretest-bug@gnu.org
Cc: ding@gnus.org
Subject: cannot start Gnus with idna.el
Date: Sat, 29 Mar 2008 08:28:45 +0900	[thread overview]
Message-ID: <86prteh1hu.fsf@ra333.heimat.gr.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

Hi,

I noticed that recent CVS Emacs has a problem. For example, Gnus cannot
start if idna.el is installed in the load-path directory.

I found the problem under the combination of

o FreeBSD/i386 8.0-CURRENT (Jan 29 2008)
o Emacs 23.0.60 (CVS HEAD)
o No Gnus 0.7 (CVS HEAD)
o GNU Libidn 1.2

I checked out the HEAD yesterday morning (JST), bootstrapped with gcc4
and ran. And then, typed ( g n u s ) C-j in *scratch* buffer but nothing
happened.

Next, I evaled (setq debug-on-quit t) and saved the *Backtrace* which
says the breakpoint is in idna.el:idna-to-ascii-response(). I attach the
*Backtrace* file.

The "while" in idna-to-ascii-response() seems infinite loop.

(defun idna-to-ascii-response ()
  (while (and (eq (process-status idna-to-ascii-process) 'run)
              (null idna-to-ascii-response))
    (accept-process-output idna-to-ascii-process 1))
  idna-to-ascii-response)

The idna-to-ascii-response is called from message.el and the failure
itself occurs in


[-- Attachment #2: Type: text/plain, Size: 32 bytes --]

(idna-to-ascii "räksmörgås")


[-- Attachment #3: Type: text/plain, Size: 256 bytes --]

Of cource, after I removed idna.el from any directories of load-path,
the error go away. (But there is another problem with Gnus which I'd
like to report.)

Regards,

Note: this report is sent using another CVS Emacs several weeks old.
-- 
NAKAJI Hiroyuki

[-- Attachment #4: Backtrace.gnus.20080328 --]
[-- Type: application/octet-stream, Size: 2648 bytes --]

             reply	other threads:[~2008-03-28 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 23:28 NAKAJI Hiroyuki [this message]
2008-05-24 12:40 ` Reiner Steib
2008-05-31 23:59   ` NAKAJI Hiroyuki
2009-01-01 17:03 ` Reiner Steib
2009-01-01 18:14   ` Reiner Steib
2010-09-26  1:59     ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86prteh1hu.fsf@ra333.heimat.gr.jp \
    --to=nakaji@jp.freebsd.org \
    --cc=ding@gnus.org \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).