From: Jeff Blaine <jblaine@mitre.org>
Subject: Re: Emacs 21.4a - Solaris 10 x86, Fatal error (11) on exit
Date: Thu, 15 Dec 2005 17:55:28 -0500 [thread overview]
Message-ID: <43A1F460.9080708@mitre.org> (raw)
In-Reply-To: <4395F794.5050304@mitre.org>
FWIW, this is solved with 21.3 by getting the CVS version
of src/unexelf.c and src/unexsol.c as of 12/15/2005 at
least.
How to get the files:
cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs \
co emacs
I would be surprised if the same did not work for 21.4
Works for SPARC and x86 Solaris 10 with GCC 3.4 (and I
bet others).
Jeff Blaine wrote:
> > I've compiled emacs21.4a on a Solaris 10 x86 box and get a
> > strange "Fatal error (11).Segmentation Fault" on exit of the emacs
> > program. Emacs seems to work okay apart from this exit error.
> > Any ideas what the problem might be?
>
> Kevin Rodgers commented:
>
> 1. The -batch command line option implies
> -q (aka -no-init-file); try
>
> ./emacs -no-site-file -batch -f list-load-path-shadows
>
> Kevin, I think this is missing the main problem.
>
> % ./emacs -no-site-file -batch -f list-load-path-shadows
> Fatal error (11).Segmentation Fault (core dumped)
> %
>
> This is on Solaris 10 for SPARC in my case, not x86. The
> problem exists back in 21.3 under Solaris 10 as well FWIW.
>
> Note, however, that as Andy Heaps mentioned above, emacs
> does in fact run (./emacs), then segfaults at exit time.
>
> Curious how there's no Emacs 21.x up on sunfreeware.com yet
> after the OS has been out for over a year now.
>
> Any ideas? I have tried both with GNU ld/as as part of
> binutils and also /usr/ccs/bin/ld (and as). Same problem
>
>
next prev parent reply other threads:[~2005-12-15 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 20:41 Emacs 21.4a - Solaris 10 x86, Fatal error (11) on exit Jeff Blaine
2005-12-07 0:24 ` Kevin Rodgers
2005-12-15 22:55 ` Jeff Blaine [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 12:46 Andy Heaps
2005-11-08 19:03 ` Kevin Rodgers
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=43A1F460.9080708@mitre.org \
--to=jblaine@mitre.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).