From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: How to get this debugged (pressing g fails)
Date: Thu, 26 Sep 2013 16:10:08 -0400 [thread overview]
Message-ID: <87ioxngx9b.fsf@newsguy.com> (raw)
In-Reply-To: <b4mob7gieyg.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
Harry Wrote:
>> I really don't have a clue how to determine what is causing it.
>> Obviously not a general problem and just as obviously its in my
>> environment somehow. But where to look, and how to look?
KatsumiY replied:
> Type `C-]' to exit the debugger.
> M-x load-library RET gnus-group.el RET
> (Note: it should be .el, not .elc)
> Type `g'
> If you get a byte-code in the backtrace, load another .el file
> and do it again. Where "another .el file" is the module that
> provides the function expressed as a byte-code in the backtrace.
Thanks for the input. I think I followed the directions closely but
didn't get anything better when I pressed 'g'.
After loading gnus-group.el and pressing 'g' I just get
the same exact debugger output:
Debugger entered: nil
gnus-group-get-new-news(nil)
call-interactively(gnus-group-get-new-news nil nil)
Maybe the bit from Messages buffer will help... Going to debugger
always happens after scanning nndraft active file.
from Messages buffer
,----
| Checking new news...
| nnimap read 2k from imap.gmail.com
| Reading active file via nnml...
| Reading incoming mail from directory...
| Wrote /home/reader/Mail/mail_cron_tr/30553
| Wrote /home/reader/Mail/mail_rsnap_tr/13838
| Reading incoming mail from file...
| nnml: Reading incoming mail (2 new)...done
| Reading active file via nnml...done
| Reading active file from archive via nnfolder...done
| Reading active file via nndraft...done
| Gnus timed out.
| Entering debugger...
`----
next prev parent reply other threads:[~2013-09-26 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 0:01 Harry Putnam
2013-09-26 0:50 ` Katsumi Yamaoka
2013-09-26 20:10 ` Harry Putnam [this message]
2013-09-26 22:50 ` Katsumi Yamaoka
2013-09-27 21:23 ` Harry Putnam
2013-10-01 14:56 ` Harry Putnam
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=87ioxngx9b.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.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).