Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Alan Mackenzie]

Hi, Jan,

Time for a top-post.  ;-)

All your answers to my questions are consistent with a bug in
c-parse-state (don't ask!).  I recently enhanced and severely optimised
this routine (it contains a cache) to deal better with certain types of
non-unusual source files.  If this cache is getting corrupted, it could
easily foul up a buffer's indentation.

Would you try one more thing, please: when you reach this buggy state
again, would you please do

    M-: (c-state-cache-init)

, and tell me if this clears the buggy state.

Thanks!



On Tue, Feb 09, 2010 at 01:45:35PM +0100, Jan Djärv wrote:
> Ok, here are some answers.
> 
> Alan Mackenzie skrev:
> >
> >OK.  Now some more details, please!
> >
> >(i) Have you ever noticed this bug happening on earlier Emacsen, in
> >  particular Emacs 23.1?
> 
> No.
> 
> >(ii) Does this bug happen every time you use Emacs this long, or only
> >  sometimes?  If the latter, how often (10%, 50%, 90%)?
> 
> 100%.  If I just keep editing it eveentually breaks.
> 
> >(iii) Do you think there might be any connection with some of the more
> >  unusual minor modes you've got switched on?  Things like
> >  auto-encryption mode?
> >
> 
> No, this doesn't seem to have any effect.
> 
> >When Emacs reaches this broken state:
> >(iv) Are all C(++) buffers in this state, or only some?  Any correlation
> >  with how many edits have been done on a buffer, or how long it's been
> >  loaded?
> 
> It is a pre buffer breakage.  One buffer usually gets borken first, while 
> the others are ok.  It is the one that I've changed/edited the most in.
> 
> >(v) What about indentation in a freshly loaded file?
> 
> No problem.
> 
> >(vi) Will M-x c-mode or M-x c++-mode clear the problem?
> 
> Yes.
> 
> >(vii) Does reverting (M-x revert-buffer) a file fix indentation?
> 
> No.
> 
> >(viii) Does killing and reloading a file fix indentation?
> 
> Yes.
> 
> >(ix) Does intentation gradually deteriorate at around 4 hours, or does it
> >  break suddenly?
> 
> Suddenly.
> 
> >(x) Do all CC Mode buffers break at the same time, or is it a "creeping
> >  death"?
> 
> Only one at the time.
> 
> 
> >Just one other thing: Could you please post a dump of your CC Mode
> >configuration (C-c C-b in a C(++) buffer).  Thanks.
> >

[ Dump appreciated! ]

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Jan D.]

Alan Mackenzie wrote:
> Hi, Jan,
> 
> Time for a top-post.  ;-)
> 
> All your answers to my questions are consistent with a bug in
> c-parse-state (don't ask!).  I recently enhanced and severely optimised
> this routine (it contains a cache) to deal better with certain types of
> non-unusual source files.  If this cache is getting corrupted, it could
> easily foul up a buffer's indentation.
> 
> Would you try one more thing, please: when you reach this buggy state
> again, would you please do
> 
>     M-: (c-state-cache-init)
> 
> , and tell me if this clears the buggy state.
> 
> Thanks!

No, it does not.  Run with Emacs taken from trunk 2010-02-24, around 
11.00 UTC.

	Jan D.

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Miles Bader]

"Jan D." <jan.h.d@swipnet.se> writes:
>>     M-: (c-state-cache-init)
>>
>> , and tell me if this clears the buggy state.
>
> No, it does not.  Run with Emacs taken from trunk 2010-02-24, around
> 11.00 UTC.

Yeah, I've been noticing the same problem a lot recently , and
(c-state-cache-init) doesn't seem to help.

Neither does re-invoking c++-mode (which in the past I've found is often
a good way to clear indentation bugs due to c++-mode caching bugs).
Deleting the buffer and re-visiting the file is the only way I've found
to get things working again.

It does seem to always occur somewhere following use of template'd
types though, so I imagine it's probs with the < and > chars.

[The annoying thing is that while it's very repeatable at the time it
occurs, it doesn't repeat for different emacs sessions, so I'm not
entirely sure how to go about reporting the bug...]

-Miles

-- 
Miss, pn. The title with which we brand unmarried women to indicate that
they are in the market. Miss, Missis (Mrs.) and Mister (Mr.) are the three
most distinctly disagreeable words in the language, in sound and sense. Two
are corruptions of Mistress, the other of Master. In the general abolition
of social titles in this our country they miraculously escaped to plague
us. If we must have them let us be consistent and give one to the unmarried
man. I venture to suggest Mush, abbreviated to Mh.

bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Alan Mackenzie]

Jan, Miles,

On Thu, Feb 25, 2010 at 09:59:06AM +0900, Miles Bader wrote:
> "Jan D." <jan.h.d@swipnet.se> writes:
> >>     M-: (c-state-cache-init)

> >> , and tell me if this clears the buggy state.

> > No, it does not.  Run with Emacs taken from trunk 2010-02-24, around
> > 11.00 UTC.

> Yeah, I've been noticing the same problem a lot recently , and
> (c-state-cache-init) doesn't seem to help.

> Neither does re-invoking c++-mode (which in the past I've found is often
> a good way to clear indentation bugs due to c++-mode caching bugs).
> Deleting the buffer and re-visiting the file is the only way I've found
> to get things working again.

Reinitialising a CC Mode doesn't clear text properties from the buffer.
Perhaps it should.

> It does seem to always occur somewhere following use of template'd
> types though, so I imagine it's probs with the < and > chars.

As always.  These little characters are horrors to deal with in C++ Mode.
Their treatment is gradually improving.

In particular, I fixed some "silly" bugs concerned with them and
committed the fix yesterday evening (UCT+2).  Hopefully, things will run
more smoothly from now on.

> [The annoying thing is that while it's very repeatable at the time it
> occurs, it doesn't repeat for different emacs sessions, so I'm not
> entirely sure how to go about reporting the bug...]

Bob did so splendidly with a dribble file and CC Mode configuration
(generated by C-c C-b).  Anyhow, it might be working properly now.

> -Miles

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Jan Djärv]

Hello.

FWIW, this bug is still present in the trunk.  I see it 5-8 times per day.
Revert buffer sometimes work to get back on track, but for the majority of 
cases, I have to kill the buffer and reopen the file for cc-mode to work again.

	Jan D.

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Andrew Hyatt]

Jan Djärv <jan.h.d@swipnet.se> writes:

> Hello.
>
> FWIW, this bug is still present in the trunk.  I see it 5-8 times per day.
> Revert buffer sometimes work to get back on track, but for the majority of
> cases, I have to kill the buffer and reopen the file for cc-mode to work again.
>
> 	Jan D.

Hi, I've been using cc-mode every day for the past few years at
work, and I don't recall seeing this bug either in Emacs 24 or 25.  Has
anyone reproduced this lately?

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Eli Zaretskii]

> From: Andrew Hyatt <ahyatt@gmail.com>
> Date: Thu, 18 Aug 2016 01:01:04 -0400
> Cc: Alan Mackenzie <acm@muc.de>, 5490@debbugs.gnu.org, emacs-devel@gnu.org
> 
> Jan Djärv <jan.h.d@swipnet.se> writes:
> 
> > Hello.
> >
> > FWIW, this bug is still present in the trunk.  I see it 5-8 times per day.
> > Revert buffer sometimes work to get back on track, but for the majority of
> > cases, I have to kill the buffer and reopen the file for cc-mode to work again.
> >
> > 	Jan D.
> 
> Hi, I've been using cc-mode every day for the past few years at
> work, and I don't recall seeing this bug either in Emacs 24 or 25.  Has
> anyone reproduced this lately?

I think it's very likely that the latest fixes by Alan in CC mode
nailed this one for good.

Re: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Andrew Hyatt]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrew Hyatt <ahyatt@gmail.com>
>> Date: Thu, 18 Aug 2016 01:01:04 -0400
>> Cc: Alan Mackenzie <acm@muc.de>, 5490@debbugs.gnu.org, emacs-devel@gnu.org
>> 
>> Jan Djärv <jan.h.d@swipnet.se> writes:
>> 
>> > Hello.
>> >
>> > FWIW, this bug is still present in the trunk.  I see it 5-8 times per day.
>> > Revert buffer sometimes work to get back on track, but for the majority of
>> > cases, I have to kill the buffer and reopen the file for cc-mode to work
>> > again.
>> >
>> > 	Jan D.
>> 
>> Hi, I've been using cc-mode every day for the past few years at
>> work, and I don't recall seeing this bug either in Emacs 24 or 25.  Has
>> anyone reproduced this lately?
>
> I think it's very likely that the latest fixes by Alan in CC mode
> nailed this one for good.

OK, I'm going to mark this one as doneunreproducible - it may have been
fixed some time in the past, or by these recent fixes you refer to.
I'll keep an eye out for this myself during my normal work, and re-open
this if I or anyone else starts seeing this again.

bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.

[Alan Mackenzie]

Hello, Andrew.

On Sun, Aug 21, 2016 at 12:57:50AM -0400, Andrew Hyatt wrote:
> Eli Zaretskii <eliz@gnu.org> writes:

> >> From: Andrew Hyatt <ahyatt@gmail.com>
> >> Date: Thu, 18 Aug 2016 01:01:04 -0400
> >> Cc: Alan Mackenzie <acm@muc.de>, 5490@debbugs.gnu.org, emacs-devel@gnu.org

> >> Jan Djärv <jan.h.d@swipnet.se> writes:

> >> > Hello.

> >> > FWIW, this bug is still present in the trunk.  I see it 5-8 times per day.
> >> > Revert buffer sometimes work to get back on track, but for the majority of
> >> > cases, I have to kill the buffer and reopen the file for cc-mode to work
> >> > again.

> >> > 	Jan D.

> >> Hi, I've been using cc-mode every day for the past few years at
> >> work, and I don't recall seeing this bug either in Emacs 24 or 25.  Has
> >> anyone reproduced this lately?

> > I think it's very likely that the latest fixes by Alan in CC mode
> > nailed this one for good.

> OK, I'm going to mark this one as doneunreproducible - it may have been
> fixed some time in the past, or by these recent fixes you refer to.
> I'll keep an eye out for this myself during my normal work, and re-open
> this if I or anyone else starts seeing this again.

Thanks.  I think this bug (which was definitely real) got fixed as a side
effect of fixing something else, and this happened quite a long time ago.

-- 
Alan Mackenzie (Nuremberg, Germany).



------------------------------------------------------------------------------