Re: Problem with current CVS and XEmacs

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Andreas Jaeger <aj@suse.de> writes:

> Jesper Harder <harder@ifa.au.dk> writes:
>
>> Andreas Jaeger <aj@suse.de> writes:
>>
>>> Starting current CVS Gnus I get with XEmacs 21.4.13:
>>>
>>> Signaling: (wrong-type-argument listp t)
>>>   gnus-read-active-file-1((nntp "gromit.moeb") nil)
>>>
>>> Everything works if I go back to:
>>> $ cvs up -D 2003-12-20 
>>>
>>> I can't see directly what's wrong, any ideas?
>>
>> You could eval `gnus-read-active-file-1' to (possibly) get a better
>> backtrace.  Or step through it with edebug to locate the place that
>> signals the error.
>
> I didn't get anything useful out of this :-(, my debug knowledge is
> too old.
>
> But I did a binary search and the patch that introduces the breakage
> is this one:
> --- ChangeLog   22 Dec 2003 11:39:06 -0000      6.2712
> +++ ChangeLog   22 Dec 2003 14:07:03 -0000      6.2713
> @@ -1,3 +1,17 @@
> +2003-12-22  Kevin Greiner <kgreiner@xpediantsolutions.com>
> +       * gnus-int.el (gnus-open-server): Fixed the server status such
> +       that an agentized server, when opened offline, has a status of
> +       offline.  Also fixes bug whereby the agent's backend was called
> +       twice to open each server.
> +
> +       * gnus-start.el (gnus-get-unread-articles-in-group): Autoload
> +       gnus-agent-possibly-alter-active rather than inline to resolve
> +       compiler warnings.
> +
> +       * gnus.el (gnus-server-to-method): Added fallback of iterating
> +       over gnus-newsrc-alist to resolve names of foreign servers.
> +       Should fix recent agent bug.
> +
>
> Note that I'm not running agentized at all,

Andreas,
My apologies for your difficulties.

Well, none of these changes obviously intersect with
gnus-read-active-file-1.  So, I'm going to need to refresh your debug
knowledge.  I'd like you to do the following on a clean (just started)
emacs.

M-x load-library gnus
M-x load-library gnus-start.el
M-x toggle-debug-on-error
M-x gnus

Please post the stack trace that you get.  If you feel comfortable
doing it, it would be helpful to also eval some of the variables
present on the first line of the stack trace.  You can do this my
typing e then a variable name in the debug buffer.

Kevin Greiner