GNU bug report logs - #6414
f->output_data.w32->menubar_widget uninitialized?

Previous Next

Full log

Message #17 received at 6414 <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 6414 <at> debbugs.gnu.org
Subject: Re: bug#6414: f->output_data.w32->menubar_widget uninitialized?
Date: Mon, 4 Jul 2011 00:19:59 +0200

On Sun, Jul 3, 2011 at 20:54, Juanma Barranquero <lekktu <at> gmail.com> wrote:
> On Sun, Jun 13, 2010 at 20:47, Lennart Borgman
> <lennart.borgman <at> gmail.com> wrote:
>
>> The problem seems to be in x_free_frame_resources. Should not
>> free_frame_menubar be called before my_destroy_window there?
>
> You reported seeing some system call errors, presumably under a
> debugger or with DebPrint statements. Did you see any bug? If so, can
> you please send a recipe to reproduce it starting with emacs -Q?

I can't do much to check it now. I do not have time to setup the
required environment on my new pc now.

However I think it is also very difficult to catch such errors. They
are likely to be race conditions (since w32 messages from different
sources are involved).

So I think it is better to check the logic. (As I have tried to above.)

And I also still think it is a good idea to add check for error
conditions after all system calls. (For the same reason as above.)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.