Re: Arghh, my Gnus is going crazy !!

[Xavier Maillard <zedek@gnu-rox.org>]

On 25 sep 2004, Kevin Greiner wrote:

> Xavier Maillard <zedek@gnu-rox.org> writes:
> 

 [ ... ]

> > Something is doing concatenation somewhere (look 794, 795 and
> > the 794795). What is that ????
> > 
> > Thank you for any hint on fixing this.
> 
> This is actually a very old problem. We've made very little
> progress with it, hence the gnus-agent-check-overview-buffer
> function, as it is rarely reproducable. I suspect that the
> actual bug is in your server and that it is sending you bad
> headers.
> 
> Let's try this first:
> 
> Delete the group's .overview and .agentview so that you fetch
> all new headers from nntp.

Problem with such tecnic is that AFAIK, it makes forget the
marks :(

> Customize nntp-nov-is-evil to set it to t. Try to open the
> group, if the problem has gone away then we know that your
> server's nov database is corrupt.

Nothing change. Err, at least, rmoving .agentview/.overview and
doing C-k on the group is the only solution I know. When doing
that, something seems to "fix" the problem.

> If that doesn't fix it, would you be willing to do a little
> debugging for me?
> 
> If so, please do the following.
> 
> Then do
> M-x load-library<ret>gnus-agent.el<ret>
> M-x gnus
> M-x debug-on-entry<ret>gnus-agent-check-overview-buffer<ret>
> 
> Now try to open the group's summary buffer. This should launch
> the debugger.

Yes it did.
 
> If I've gotten this right, the stack trace should show that
> gnus-agent-check-overview-buffer was called by
> gnus-agent-fetch-headers. The current buffer should contain the

Not exactly but no problem.

> raw headers returned by nntp. How do they look? If they look

I didn't get any "raw nntp headrs" buffer here. When it say it
entered function blah-blah, hitting on 'c' open the summary
buffer.

-- 
"sometimes i feel like we're making emacs better and better because we don't 
 know what to do with emacs once it is finished."

    -- AlexSchroeder on #emacs @OPN