[debbugs-tracker] bug#16070: closed (24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= start && end <= c->buffer_end)

[GNU bug Tracking System]

Your message dated Sat, 07 Dec 2013 10:35:25 +0200
with message-id <address@hidden>
and subject line Re: bug#16070: 24.3.50; Crash, Emacs fatal error: assertion 
failed: c->buffer_beg <= start     &&      end <= c->buffer_end
has caused the debbugs.gnu.org bug report #16070,
regarding 24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= 
start && end <= c->buffer_end
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16070: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16070
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= start && end <= c->buffer_end
>
>
>
>
> Date: 
>
> Fri, 06 Dec 2013 19:43:36 +0900
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
>
>
>
>
> Emacs crashed while cycling through [(info "(org) Visibility cycling")]  a org
> file.
>
> backtrace is attached
>
>
> --
> ఎందరో మహానుభావులు అందరికి వందనములు.
> YYR
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#16070: 24.3.50; Crash, Emacs fatal error: assertion failed: c->buffer_beg <= start	&&	end <= c->buffer_end
>
>
>
>
> Date: 
>
> Sat, 07 Dec 2013 10:35:25 +0200
>
>
>
>
> > From: Yagnesh Raghava Yakkala <address@hidden>
> > Cc: address@hidden
> > Date: Sat, 07 Dec 2013 14:53:03 +0900
> > 
> > >> When opened attached org as follows, it automatically crashes on my 
> > >> system. 
> > >> emacs -Q test.org -eval "(set-buffer-multibyte nil)"
> > >
> > > Thanks.  That particular crash is fixed in trunk revision 115399,
> > 
> > Thanks and I can confirm.
> > 
> > > (did you also toggle buffer's multibyteness there, after visiting the
> > > file?).
> > 
> > Yes.
> > 
> > > If the problem is not entirely fixed, please show the recipe to reproduce
> > > the problem.
> > 
> > I can't reproduce original problem now. I think we can close this bug now.  
>
> Thanks, closing.
>
>
> --- End Message ---