Bug 489066 - emacsclient x86_64 segfaults when connecting to a tcp emacs server
emacsclient x86_64 segfaults when connecting to a tcp emacs server
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
10
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Novotny
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-06 19:51 EST by Elliott Johnson
Modified: 2009-03-27 10:51 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-27 10:51:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
A patch to include the proper headers to prevent segfaulting on x86_64 systems running emacsclient (299 bytes, patch)
2009-03-06 19:51 EST, Elliott Johnson
no flags Details | Diff

  None (edit)
Description Elliott Johnson 2009-03-06 19:51:47 EST
Created attachment 334376 [details]
A patch to include the proper headers to prevent segfaulting on x86_64 systems running emacsclient

Description of problem:

On x86_64 systems, emacsclient will segfault when connecting to a tcp based emacs server.

Version-Release number of selected component (if applicable):

emacs-common-22.3-3.fc10.x86_64

How reproducible:

Always

Steps to Reproduce:
1. start emacs
2. set emacs server to use tcp sockets "M-: (setq server-user-tcp t)"
3. start the emacs server "M-x server-start"
4. In a shell use emacsclient to connect to the tcp socket
    $ emacsclient -f ~/.emacs.d/server/server file.to.edit
  
Actual results:

Segfault

Expected results:

For the file to open in the emacs server for editing.

Additional info:

Attached is a patch to include the proper header, which fixes the problem.
Comment 1 Daniel Novotny 2009-03-27 10:51:39 EDT
thanks for the patch

included in emacs-22.3-10.fc11

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