Bug 633359 - Emacs crash produced unusable backtrace
Summary: Emacs crash produced unusable backtrace
Keywords:
Status: CLOSED DUPLICATE of bug 730169
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-13 16:26 UTC by Christopher Beland
Modified: 2013-03-03 23:01 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-29 14:01:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christopher Beland 2010-09-13 16:26:23 UTC
Emacs crashed - not sure in what situation, I just found the crash in ABRT's list.  When I tried to report it, I got the error "Reporting disabled because backtrace is unusable".  "debuginfo-install emacs" has installed everything it can.  I did experience an emacs crash as root (which I successfully reported earlier), but this crash is listed under user:cbeland.

abrt-1.1.13-2.fc14.x86_64
emacs-23.2-7.fc14.x86_64

---

BFD: Warning: /var/spool/abrt/ccpp-1284387087-2906/coredump is truncated: expected core file size >= 27025408, found: 61440.
warning: core file may not match specified executable file.
[New Thread 2906]
[New Thread 2907]
Cannot access memory at address 0x3453221228
Cannot access memory at address 0x3453221228
Cannot access memory at address 0x3453221228
Failed to read a valid object file image from memory.
Core was generated by `emacs'.
Program terminated with signal 7, Bus error.
#0  0x0000003453434367 in ?? ()

Thread 2 (Thread 2907):
#0  0x00000034534db093 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7f50b02f9b90

Thread 1 (Thread 2906):
#0  0x0000003453434367 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fff16972038
From                To                  Syms Read   Shared Object Library
0x0000003453000b40  0x0000003453019ee6  Yes         /lib64/ld-linux-x86-64.so.2
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
rax            0x0	0
rbx            0x7	7
rcx            0xffffffffffffffff	-1
rdx            0xb5a	2906
rsi            0x7	7
rdi            0xb5a	2906
rbp            0x0	0x0
rsp            0x7fff16972038	0x7fff16972038
r8             0x0	0
r9             0x0	0
r10            0x8	8
r11            0x206	518
r12            0x0	0
r13            0x0	0
r14            0x0	0
r15            0x40	64
rip            0x3453434367	0x3453434367
eflags         0x206	[ PF IF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
No function contains program counter for selected frame.

Comment 1 RHEVM Bugzilla Bot 2011-08-28 15:10:41 UTC
"Shahar Havivi (shaharh) submitted a patch to fix this issue. Proposed patch: http://rhevm-gerrit.usersys.redhat.com/1399"

Comment 2 RHEVM Bugzilla Bot 2011-08-29 13:29:05 UTC
"Shahar Havivi (shaharh) submitted a new patch, replacing the existing one. New proposed patch: http://rhevm-gerrit.usersys.redhat.com/1399"

Comment 3 Shahar Havivi 2011-09-01 07:06:51 UTC
Please ignore the "RHEVM Bugzilla Bot"

Comment 4 Jiri Moskovcak 2011-11-29 14:01:04 UTC
Probably a dupe of #730169

*** This bug has been marked as a duplicate of bug 730169 ***


Note You need to log in before you can comment on or make changes to this bug.