unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 8705@debbugs.gnu.org
Subject: bug#8705: 23.3; Emacs occasionally crashes (segfault) just after starting it
Date: Fri, 20 May 2011 14:59:19 +0200	[thread overview]
Message-ID: <20110520125919.GJ1581@prunille.vinc17.org> (raw)
In-Reply-To: <83r57tfvot.fsf@gnu.org>

On 2011-05-20 14:38:58 +0300, Eli Zaretskii wrote:
> > Date: Fri, 20 May 2011 13:16:01 +0200
> > From: Vincent Lefevre <vincent@vinc17.net>
> > Cc: 8705@debbugs.gnu.org
> > 
> > On 2011-05-20 13:40:34 +0300, Eli Zaretskii wrote:
> > > All of your reported crashes seem to be in a call to `getenv', which
> > > is a library function, called by GTK routines deep in the GTK code.
> > > It is hard to imagine that they could be Emacs problems, especially
> > > since you see them since Emacs 22.
> > 
> > Unless Emacs has corrupted the memory earlier.
> 
> That's definitely a possibility.  However, it is strange that only you
> see these problems for several versions.  If Emacs corrupts memory so
> early into the session, many other users would be affected.

No, because other users have a different configuration. I'm quite
sure that the configuration matters as I got such crashes on
different machines (where I use the same config).

By configuration, I mean the .emacs, but also the graphical
environment (e.g. the window manager, fvwm in my case, and its
configuration). That wouldn't be the first time an application
is affected by the window manager. See

  https://bugzilla.mozilla.org/show_bug.cgi?id=551678

for instance, where I could reproduce a bug only with manual/active
placement.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)





  reply	other threads:[~2011-05-20 12:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  8:54 bug#8705: 23.3; Emacs occasionally crashes (segfault) just after starting it Vincent Lefevre
2011-05-20  9:12 ` Vincent Lefevre
2011-05-20 10:40 ` Eli Zaretskii
2011-05-20 11:16   ` Vincent Lefevre
2011-05-20 11:38     ` Eli Zaretskii
2011-05-20 12:59       ` Vincent Lefevre [this message]
2011-09-20 14:51     ` Vincent Lefevre
2012-07-06 11:13       ` Vincent Lefevre
2012-07-06 20:32         ` Troels Nielsen
2012-07-06 22:51           ` Daniel Colascione
2012-07-07 15:08             ` Troels Nielsen
2014-09-22 13:06 ` Vincent Lefevre
2014-09-27  4:10   ` Stefan Monnier
2014-10-09 20:03     ` Glenn Morris
2014-10-12  2:40 ` bug#8705: Emacs 24.3 " Paul Eggert
2014-10-12  6:19   ` Paul Eggert
2014-10-14 18:36   ` Stefan Monnier
2014-10-14 18:44     ` Glenn Morris
2014-10-14 18:45       ` Glenn Morris
2014-10-14 18:52       ` Glenn Morris

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=20110520125919.GJ1581@prunille.vinc17.org \
    --to=vincent@vinc17.net \
    --cc=8705@debbugs.gnu.org \
    --cc=eliz@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 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).