Uwe Brauer wrote:
>>>>>"Simon" == Simon Josefsson
<jas(a)extundo.com> writes:
>>>>>
>>>>>
>>
>> Ok that works, however since the process get stacked I don't get any
>> reasonable backtrace.
Simon> I don't understand. Does XEmacs freeze completely? If so, I don't
Simon> think there is anything we can do at the Elisp level. It must be
Simon> debugged as an XEmacs bug.
No what I say is: I want to copy that msg and xemacs starts to tell me
copying msg, but nothing happens after 2 min after several Control g I
can type again, however it seems that the nnimap command is stacked, I
cannot leave the group nor the server, but I have to do what you told
me.
So for me it not clear who is to blame. However that problem does not
occur in gnu emacs with the same gnus (ngnus 0.3)
a backtrace would help. i assume you're running under linux? you can
do `ps -auxww' or `ps -edalf' or something like that to list all
processes, and then attach to the xemacs process that's hung, and do
`where' to get a c backtrace and `call debug_backtrace()' to get a lisp
backtrace. one of the faq questions in section 2.4 covers this in more
detail.
ben