all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: CVS emacs crashes right after startup
Date: Wed, 04 Feb 2004 20:36:04 +0200	[thread overview]
Message-ID: <2914-Wed04Feb2004203604+0200-eliz@elta.co.il> (raw)
In-Reply-To: <jwv65emohzf.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (message from Stefan Monnier on 04 Feb 2004 12:47:22 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: 04 Feb 2004 12:47:22 -0500
> 
> As a reader, I'd think "damn, why can't they fix it so I can save 6MB and
> startup faster"?

I strongly suspect that the difference in sizes is due to debug info
(thus doesn't affect startup time at all), and that the extra debug
info is confusing unexec to the point that it produces a bad binary.

Alas, I have no access to a Solaris machine with GCC and Binutils, not
to mention a total lack of time to work on this even if I did.

  reply	other threads:[~2004-02-04 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <q5g3carew8j.fsf@lucent.com>
     [not found] ` <q5goeteekqq.fsf@lucent.com>
     [not found]   ` <uvfnm7el3.fsf@elta.co.il>
     [not found]     ` <q5gr7y5xq7w.fsf@lucent.com>
     [not found]       ` <q5gd69gjfpg.fsf@lucent.com>
2004-01-19 21:01         ` CVS emacs crashes right after startup Eli Zaretskii
2004-02-02 12:03           ` Klaus Zeitler
2004-02-02 18:49             ` Eli Zaretskii
2004-02-03 14:35             ` Richard Stallman
2004-02-04 10:19               ` Klaus Zeitler
2004-02-04 11:14                 ` Eli Zaretskii
2004-02-05  9:27                   ` Klaus Zeitler
2004-02-04 17:47                 ` Stefan Monnier
2004-02-04 18:36                   ` Eli Zaretskii [this message]
2004-02-18  5:55                 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2914-Wed04Feb2004203604+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.