Subject: Re: bug#11717: 24.1.50; Segmentation fault in Fdelete_other_windows_internal when running Gnus unit tests

From: Eli Zaretskii <[email-masked]>
Date: Fri, 15 Jun 2012 23:02:36 +0300

> From: David Engster <[email-masked]>
> Cc: [email-masked]
> Date: Fri, 15 Jun 2012 21:00:29 +0200
> 
> Regarding MOUSE_HL_INFO, I guess this
> 
> (gdb) p f->output_data
> $6 = {
>   tty = 0x0,
>   x = 0x0,
>   w32 = 0x0,
>   ns = 0x0,
>   nothing = 0
> }
> 
> doesn't play well with either expression which might get executed in the
> macro. FRAME_WINDOW_P(f) is false since output_method is
> 'output_initial', hence it tries to access
> output_data.tty->display_info->mouse_highlight.

Does it help to condition the entire portion that accesses and uses
hlinfo by 'if (!noninteractive)' ?

But what I don't understand is why are we calling delete-other-windows
when we are running in batch mode?  Isn't that a bug as well?