unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: markus.hoenicka@mhoenicka.de
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17753@debbugs.gnu.org
Subject: bug#17753: Cygwin emacs-X11 core dump
Date: Sat, 14 Jun 2014 00:53:04 +0200	[thread overview]
Message-ID: <21403.32976.771019.763973@wombat.mininet> (raw)
In-Reply-To: <83mwdjzeon.fsf@gnu.org>

Eli Zaretskii writes:
 > > Date: Wed, 11 Jun 2014 08:16:39 +0200
 > > From: Markus Hoenicka <markus.hoenicka@mhoenicka.de>
 > > Cc: 17753@debbugs.gnu.org
 > > 
 > > > Are you sure you were in the right thread when you collected the
 > > > backtrace?
 > > > 
 > > 
 > > No, I'm not sure at all. How do I find out?
 > 
 > "info threads" will display all the threads.  "thread apply all bt"
 > will produce a backtrace for every thread.

Ok, here goes:

(gdb) info threads
  Id   Target Id         Frame
  9    Thread 0xe14      0x0004003300001f80 in ?? ()
  8    Thread 0xb48      0x9e84003300001f80 in ?? ()
  7    Thread 0x8fc      0x0005003300001f80 in ?? ()
  6    Thread 0xc20      0x0005003300001f80 in ?? ()
  5    Thread 0x8dc      0x0000003300001f80 in ?? ()
  4    Thread 0xf34      0x0000003300001f80 in ?? ()
  3    Thread 0xda0      0x0000003300001f80 in ?? ()
  2    Thread 0x64c      0x0000003300001f80 in ?? ()
* 1    Thread 0x6d8      0x0000003300001fa4 in ?? ()
(gdb) thread apply all bt

Thread 9 (Thread 0xe14):
#0  0x0004003300001f80 in ?? ()
#1  0x0000000000000000 in ?? ()

Thread 8 (Thread 0xb48):
#0  0x9e84003300001f80 in ?? ()
#1  0x000007fefd5410dc in ?? ()
#2  0x0000000000000000 in ?? ()

Thread 7 (Thread 0x8fc):
#0  0x0005003300001f80 in ?? ()
#1  0x000007fefd5410dc in ?? ()
#2  0x0000000000000000 in ?? ()

Thread 6 (Thread 0xc20):
#0  0x0005003300001f80 in ?? ()
#1  0x000007fefd5410dc in ?? ()
#2  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x8dc):
#0  0x0000003300001f80 in ?? ()
#1  0x000007fefd5411a2 in ?? ()
---Type <return> to continue, or q <return> to quit---
#2  0x00000000035caba8 in ?? ()
#3  0x0000000600042280 in ?? ()
#4  0x0000000000000003 in ?? ()
#5  0x00000001802de988 in ?? ()
#6  0x00000000000000c6 in ?? ()
#7  0x000000018010bc01 in ?? ()
#8  0x0000000000000048 in ?? ()
#9  0x0000000000000001 in ?? ()
#10 0x0000000000000000 in ?? ()

Thread 4 (Thread 0xf34):
#0  0x0000003300001f80 in ?? ()
Cannot access memory at address 0xffffc458

(gdb) thread apply 3 bt

Thread 3 (Thread 0xda0):
#0  0x0000003300001f80 in ?? ()
#1  0x00000000774fb037 in ?? ()
#2  0x0000000000000002 in ?? ()
#3  0x0000000000000000 in ?? ()
(gdb) thread apply 2 bt

Thread 2 (Thread 0x64c):
#0  0x0000003300001f80 in ?? ()
#1  0x000007fefd541a7a in ?? ()
#2  0x000000000042ce00 in ?? ()
#3  0x0000000100629773 in run_timers ()
    at /usr/src/debug/emacs-24.3.90-1/src/atimer.c:364
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) thread apply 1 bt

Thread 1 (Thread 0x6d8):
#0  0x0000003300001fa4 in ?? ()
#1  0x0000000100a49832 in bss_sbrk_buffer ()
#2  0x000000000042ccf0 in ?? ()
#3  0x0000000000000004 in ?? ()
#4  0x0000000101013c48 in bss_sbrk_buffer ()
#5  0x0000000000425170 in ?? ()
#6  0x000000010052b64d in CHAR_TABLE_REF (
    ct=<error reading variable: Cannot access memory at address 0x4251a000000010>,
    ct@entry=<error reading variable: Cannot access memory at address 0x4251a000000008>,
    idx=<error reading variable: Cannot access memory at address 0x4251a000000018>) at /usr/src/debug/emacs-24.3.90-1/src/lisp.h:1468


As for thread 2 I'd like to mention that there were several hints on
the Cygwin list that 64 bit Emacs has a timer-related problem, see
e.g. the thread around this post:

https://cygwin.com/ml/cygwin/2014-05/msg00419.html

In brief, I've noticed several error messages in a previous version of
64 bit Cygwin Emacs that did not cause Emacs to crash but indicated
timer-related malfunctions anyway:

Args out of range: [t 21335 39727 373923 0.5 blink-cursor-timer-function nil nil 100000], 4


Invalid function: #[(timer) "^H >^H

    ^[\211^203^Q^@Ã^H	    \"^Q^K\203^Z^@Ã^H

\"^R^L\206^_^@^K*\207" [timer timer-list timer-idle-list cell2 cell1 delq] 4 2245674]


timer-relative-time: Wrong type argument: vectorp, [t1 time high low micro pico nil 3 0 2 ...]

I've never noticed any of these messages on the other 64 bit platforms
that I use Emacs on, i.e. FreeBSD 10 and Debian testing.

Hope this helps
Markus


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





  reply	other threads:[~2014-06-13 22:53 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 21:55 bug#17753: Cygwin emacs-X11 core dump markus.hoenicka
2014-06-11  2:51 ` Eli Zaretskii
2014-06-11  6:16   ` Markus Hoenicka
2014-06-11 14:47     ` Eli Zaretskii
2014-06-13 22:53       ` markus.hoenicka [this message]
2014-06-11 12:28   ` Ken Brown
2014-06-11 15:03     ` Eli Zaretskii
2014-07-04 21:21 ` markus.hoenicka
2014-07-05 14:03   ` Ken Brown
2014-07-07 21:31     ` markus.hoenicka
2014-07-09 13:57       ` Ken Brown
2014-07-09 14:30         ` Markus Hoenicka
2014-09-17  9:45           ` Markus Hoenicka
2014-09-17 10:16             ` Eli Zaretskii
2014-09-17 10:52               ` Eli Zaretskii
2014-09-17 11:04                 ` Markus Hoenicka
2014-09-17 15:17               ` Ken Brown
2014-09-17 17:06                 ` Eli Zaretskii
2014-09-22  7:14                   ` Markus Hoenicka
2014-09-22 13:32                     ` Ken Brown
2014-09-22 14:04                       ` Markus Hoenicka
2014-09-22 14:48                         ` Eli Zaretskii
2014-10-07  7:02                   ` Markus Hoenicka
2014-10-07 14:56                     ` Ken Brown
2014-10-07 15:05                       ` Eli Zaretskii
2014-10-07 16:05                         ` Markus Hoenicka
2014-10-07 17:04                           ` Eli Zaretskii
2014-10-07 20:48                             ` Markus Hoenicka
2014-10-09  8:17                             ` Markus Hoenicka
2014-10-09  8:56                               ` Eli Zaretskii
2014-10-09  9:08                                 ` Markus Hoenicka
2014-10-09 10:35                                   ` Eli Zaretskii
2014-10-09 10:44                                     ` Markus Hoenicka
2014-10-09 11:22                                       ` Eli Zaretskii
2014-10-09 11:47                                         ` Markus Hoenicka
2014-10-09 11:55                                           ` Eli Zaretskii
2014-10-11 15:31                                             ` Ken Brown
2014-10-12  0:07                                               ` Markus Hoenicka
2014-10-20 10:59                                               ` Markus Hoenicka
2014-10-20 11:29                                                 ` Ken Brown
2014-10-20 12:04                                                   ` martin rudalics
2014-10-20 13:05                                                     ` Ken Brown
2014-10-20 14:11                                                   ` Markus Hoenicka
2014-10-20 14:37                                                   ` Markus Hoenicka
2014-10-20 15:24                                                     ` Eli Zaretskii
2014-10-20 15:29                                                       ` Markus Hoenicka
2014-10-24 21:27                                                         ` Ken Brown
2014-10-24 21:42                                                           ` Markus Hoenicka
2014-12-03 12:43                                                           ` Markus Hoenicka
2014-12-03 14:12                                                             ` Ken Brown
2014-10-20 15:29                                                   ` Eli Zaretskii
2014-10-07 16:05                       ` Markus Hoenicka
2014-07-28 22:45         ` markus.hoenicka
2014-08-06 22:02         ` markus.hoenicka
2014-10-07 16:47 ` Achim Gratz
2014-10-07 18:43   ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21403.32976.771019.763973@wombat.mininet \
    --to=markus.hoenicka@mhoenicka.de \
    --cc=17753@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).