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: Sat, 14 Jun 2014 00:53:04 +0200

Eli Zaretskii writes:
 > > Date: Wed, 11 Jun 2014 08:16:39 +0200
 > > From: Markus Hoenicka <address@hidden>
 > > Cc: address@hidden
 > > 
 > > > 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>,
    address@hidden<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

    address@hidden          \"address@hidden

\"address@hidden" [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 via email to

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