Bug 237177

Summary: Emacs segfaults when invoked as 'emacs -q'
Product: [Fedora] Fedora Reporter: Khem Raj <raj.khem>
Component: emacsAssignee: Chip Coldwell <coldwell>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-21 15:20:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
core file none

Description Khem Raj 2007-04-19 20:52:29 UTC 
Description of problem:

I tried to start emacs from my shell 'emacs -q' command and also with simple
emacs command. In both cases it segfaulted.

Version-Release number of selected component (if applicable):
emacs-22.0.95-1.fc7

How reproducible:


Steps to Reproduce:
1. Install FC7 Test3 and yum update it to very latest.
2. Install emacs
3. Run 'emacs' or 'emacs -q'
  
Actual results:
Fatal error (11)Segmentation fault


Expected results:
I expected it to launch emacs editor

Additional info:

I dumped the core and gdb'ed it

Program terminated with signal 11, Segmentation fault.
#0  0x00c90402 in __kernel_vsyscall ()
(gdb) bt
#0  0x00c90402 in __kernel_vsyscall ()
#1  0x06eb6366 in ?? ()
#2  0x080f40ff in ?? ()
#3  0x00006ae5 in ?? ()
#4  0x0000000b in ?? ()
#5  0x00000000 in ?? ()
(gdb)
Comment 1 Chip Coldwell 2007-04-20 15:05:33 UTC 
(In reply to comment #0)
> 
> I dumped the core and gdb'ed it

Can you put the core somewhere where I can get it?

Chip
Comment 2 Khem Raj 2007-04-20 22:01:40 UTC 
Created attachment 153220 [details]
core file

here is compressed core file.
Comment 3 Chip Coldwell 2007-04-23 19:19:17 UTC 
It looks like emacs is catching a signal before the auto-save-list-file-name has
been initialized, and that is causing the segfault.  A more interesting question
is why is emacs getting a signal when you start with the "-q" switch.

Could you run this and post the output to this bug?

strace -e trace=exit_group -e signal=\!sigio emacs -q
Comment 4 Khem Raj 2007-04-23 20:46:00 UTC 
here it comes.

strace -e trace=exit_group -e signal=\!sigio emacs -q
--- SIGCHLD (Child exited) @ 0 (0) ---
--- SIGCHLD (Child exited) @ 0 (0) ---
--- SIGCHLD (Child exited) @ 0 (0) ---
--- SIGCHLD (Child exited) @ 0 (0) ---
--- SIGCHLD (Child exited) @ 0 (0) ---

(emacs:20950): 4-CRITICAL **: 4: assertion `\xff\xff\xff\xff' failed
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 20950 detached
Comment 5 Chip Coldwell 2007-05-07 14:59:54 UTC 
Could you try turning off SELinux and see if the bug reproduces?

Chip
Comment 6 Khem Raj 2007-05-07 18:20:18 UTC 
(In reply to comment #5)
> Could you try turning off SELinux and see if the bug reproduces?
> 
> Chip
> 

yes SELinux is turned off. My machine is a Core 2 duo machine(64 bit) running 
32-bit Fedora
Comment 7 Chip Coldwell 2007-05-13 13:31:18 UTC 
I think this is very likely a duplicate of bug 239344; could you report your
glibc version, please?
Comment 8 Khem Raj 2007-05-14 19:15:04 UTC 
(In reply to comment #7)
> I think this is very likely a duplicate of bug 239344; could you report your
> glibc version, please?

glibc-2.5.90-22, which I think is latest. I just reinstalled emacs rpms and 
gave it another try but I got segfault

Fatal error (11)Segmentation fault
Comment 9 Chip Coldwell 2007-05-16 13:25:12 UTC 
Could you try downgrading to glibc-2.5.90-21 and see if the problem goes away?
Comment 10 Chip Coldwell 2007-05-21 15:20:49 UTC 

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