bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#17753: Cygwin emacs-X11 core dump


From: Markus Hoenicka
Subject: bug#17753: Cygwin emacs-X11 core dump
Date: Tue, 07 Oct 2014 18:05:14 +0200
User-agent: Roundcube Webmail

Am 2014-10-07 16:56, schrieb Ken Brown:
On 10/7/2014 3:02 AM, Markus Hoenicka wrote:
#0 0x00000003ff120d78 in dbus_watch_handle () at /usr/bin/cygdbus-1-3.dll
#1  0x00000003ff105799 in dbus_bus_remove_match () at
/usr/bin/cygdbus-1-3.dll
#2  0x00000003ff106580 in dbus_connection_get_dispatch_status ()
     at /usr/bin/cygdbus-1-3.dll
#3  0x00000003ff5f17d3 in
cygatspi-0!atspi_key_listener_sync_type_get_type ()
     at /usr/bin/cygatspi-0.dll
#4  0x00000003fe7bd3fe in g_main_context_prepare
(context=context@entry=0x600109540, priority=priority@entry=0x429908)
     at /usr/src/debug/glib2.0-2.38.2-4/glib/gmain.c:3340
#5  0x00000003fe7bdc32 in g_main_context_iterate
(context=context@entry=0x600109540, block=block@entry=0,
dispatch=dispatch@entry=0, self=<optimized out>)
     at /usr/src/debug/glib2.0-2.38.2-4/glib/gmain.c:3693
#6  0x00000003fe7bddb8 in g_main_context_pending (context=0x600109540)
     at /usr/src/debug/glib2.0-2.38.2-4/glib/gmain.c:3739
#7  0x00000001005b2760 in xg_select (fds_lim=<optimized out>,
rfds=rfds@entry=0x429fa0, wfds=wfds@entry=0x429fb0, efds=efds@entry=0x0,
timeout=timeout@entry=0x429fc0, sigmask=sigmask@entry=0x0)
     at /usr/src/debug/emacs-24.3.93-3/src/xgselect.c:149

It's nice to finally see what looks like a reasonable backtrace.  To
get more information about frames 0--3, you'll need to install some
more debuginfo packages:  at-spi2-atk-debuginfo,
at-spi2-core-debuginfo, and dbus-debuginfo.  I don't know if it's
possible at this point to get gdb to read the debug information for
cygdbus-1-3.dll and cygatspi-0.dll (once you install the debuginfo
packages) or if you have to wait for the next crash.  I'm sure Eli
knows.

Ken

Hi,

I just installed these additional packages. As I had to close the gdb window anyway, I'll wait for the next crash. Actually there was another crash (kindof) this afternoon, before I got round to installing the debuginfo packages. The crashes seem to come in pairs, for whatever reason. In any case, this crash left gdb spinning one of my two CPUs at full speed before it printed any debug information. I pulled the plug on the gdb process after like 20 min as it did not seem to lead anywhere.

regards,
Markus

--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38






reply via email to

[Prev in Thread] Current Thread [Next in Thread]