Re: xdisp.c problem?

[Tak Ota]

Thu, 30 Jan 2003 12:51:03 +0900 (JST): Kenichi Handa <address@hidden> wrote:

> In article <address@hidden>, Tak Ota <address@hidden> writes:
> >>  > 2003-01-29  Kenichi Handa  <address@hidden>
> >>  >         * xdisp.c (set_cursor_from_row): Pay attention to string display
> >>  >         properties.
> >>  
> >>  > This change causes emacs to get hung when I try to view a message of
> >>  > the following type.  Switching back to the old xdisp.c eliminates the
> >>  > problem.
> >>  
> >>  > Content-Type: text/html; charset="euc-kr"
> >>  
> >>  Could you show me exactly what to do to reproduce that bug?
> 
> > I tried to isolate the case from the entire circumstance, which is
> > using Mew package to view email messages.  I was not successful.  It
> > happens only when I try to view certain messages.  C-g does not break
> > emacs once it gets trapped in this situation.  There is one more fact
> > I have gained by tracing elisp execution.  The last lisp function
> > called is `overlay-put' and the emacs stops responding after that.  I
> > used C debugger to follow the trace from entry to `overlay-put' but
> > could not conclusion anything meaningful.
> 
> Please check if Emacs is in an infinite loop or not, and if
> it's in an infinite loop, find in which part of code it's
> executing.

Yes, Emacs is looping infinitely.  It is spinning busily inside
command_loop_2 which calls internal_condition_case which calls
command_loop_1 which calls read_key_sequence.  Somewhere down in
read_key_sequence is thrown an exception.  The longjump lands back in
setjmp in the internal_condition_case which returns to
command_loop_2.  This repeats forever.

I tried to find what exception it is and from where in the downstream
of read_key_sequence it is thrown, then I ran out of my time for now.
I'll continue the pursuit later.

-Tak