Re: Segfault in Emacs 23 with multi-tty

[Daniel Hackney]

On 12/9/07, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> "Daniel Hackney" <dan@haxney.org> writes:
>
>   > While testing the new multi-tty feature, I came across a segfault. I 
> started up
>   > an instance of emacs-snapshot in a terminal with the following command:
>   >
>   >  $ emacs-snapshot -q -nw --eval "(setq server-name \"editor\")" -f 
> server-start
>   >
>   > I then opened a second terminal and ran:
>   >
>   >  $ emacsclient -s editor -e '(ignore)'
>   >
>
> Thank you for your bug report.
>
> This works fine for me for emacs checked today from the CVS branch
> emacs-unicode-2 (i.e. what you call Emacs 23).
>
> Please try a more up to date version and report again here if you have
> any problems.

I tried the current emacs-unicode-2 branch which I got using git from
git://git.sv.gnu.org/emacs.git, using the commit
65a977059896b030055ff2b39513c32962519b6b. I compiled with

 $ ./configure --prefix=/home/frochild/Projects/emacs-bin --with-gtk
--with-xft CFLAGS="-O0 -g"

as recommended.

It did not segfault, but when closing the GTK window, the following was written
to stderr of the server instance:

(emacs:26151): Gdk-CRITICAL **: gdk_screen_get_display: assertion
`GDK_IS_SCREEN (screen)' failed

(emacs:26151): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(emacs:26151): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE
(instance)' failed

(emacs:26151): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed

(emacs:26151): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.14.1/gobject/gsignal.c:2180: invalid unclassed
object pointer for value type `GdkScreen'

(emacs:26151): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.14.1/gobject/gsignal.c:2180: invalid unclassed
object pointer for value type `GdkScreen'

(emacs:26151): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

The server did not terminate, however, so it is not that big of a problem. The
only issue is that unless it is redirected, this debug output is written to the
terminal on top of the existing emacs process, creating some garbage until C-l
is pressed. I do not know if this is beyond the scope of this bug report, but it
would be nice if GTK errors did not get written over an existing emacs terminal.

Recompiling without "-g" did not change this output.

-- 
Daniel M. Hackney