unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 7098@debbugs.gnu.org
Subject: bug#7098: Emacs24 crash with segmentation fault
Date: Sat, 25 Sep 2010 11:35:06 +0200	[thread overview]
Message-ID: <874odecgj9.fsf@tux.homenetwork> (raw)
In-Reply-To: <AANLkTi=gUYpdbZizVU_Kvd3O+MZ-E7R4_HgwLeY7e+6-@mail.gmail.com> (Juanma Barranquero's message of "Sat, 25 Sep 2010 11:25:37 +0200")

Juanma Barranquero <lekktu@gmail.com> writes:

> On Sat, Sep 25, 2010 at 10:23, Thierry Volpiatto
> <thierry.volpiatto@gmail.com> wrote:
>
>> Yes, i will try first to find a day, i am actually on last commit of 20
>> sept, if it crash i will go on last commit of 19 and so on.
>> Once i find the good commit it should be easy to track all commits of
>> one day, maybe with git-bisect between good and last bad.
>
> A couple of questions:
>
> - Are you using GCC 4.4.0 or later?
4.4.3

> - Does the crash happen both with optimized and non-optimized builds?
What is optimized and non-optimized builds?

> I ask because I've been getting garbage collection crashes for a while
> with non-optimized builds built with GCC 4.4.0, 4.5.0, 4.5.1, etc. The
> problem disappears if I revert back to GCC 3.4.5 or build with
> optimizations.
>
>     Juanma
>

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 





  reply	other threads:[~2010-09-25  9:35 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 17:53 bug#7098: Emacs24 crash with segmentation fault Thierry Volpiatto
2010-09-24 18:18 ` Eli Zaretskii
2010-09-24 19:14   ` Eli Zaretskii
2010-09-24 19:32     ` Thierry Volpiatto
2010-09-24 19:48       ` Eli Zaretskii
2010-09-27  8:54     ` Thierry Volpiatto
2010-09-27 10:53       ` Eli Zaretskii
2010-09-27 12:43         ` Thierry Volpiatto
2010-09-27 13:56           ` Eli Zaretskii
2010-09-27 14:06             ` Thierry Volpiatto
2010-09-27 15:43               ` Eli Zaretskii
2010-09-28  7:48                 ` Thierry Volpiatto
2010-09-24 19:23   ` Thierry Volpiatto
2010-09-24 19:36     ` Eli Zaretskii
2010-09-24 19:58       ` Thierry Volpiatto
2010-09-24 20:14         ` Eli Zaretskii
2010-09-25  7:40           ` Thierry Volpiatto
2010-09-25  8:10             ` Eli Zaretskii
2010-09-25  8:23               ` Thierry Volpiatto
2010-09-25  9:25                 ` Juanma Barranquero
2010-09-25  9:35                   ` Thierry Volpiatto [this message]
2010-09-25 11:13                     ` Juanma Barranquero
2010-09-25 11:39                       ` Thierry Volpiatto
2010-09-25 11:59                         ` Eli Zaretskii
2010-09-25 12:32                           ` Thierry Volpiatto
2010-09-25 21:26                           ` Thierry Volpiatto
2010-09-26  5:25                             ` Thierry Volpiatto
2010-09-25 12:01                         ` Juanma Barranquero
2010-09-25 12:45                           ` Thierry Volpiatto
2010-09-25 20:45                             ` Juanma Barranquero
2010-12-06 20:39 ` Chong Yidong
2010-12-06 21:15   ` Thierry Volpiatto
2010-12-09  7:25   ` Thierry Volpiatto
2010-12-15  1:50     ` Chong Yidong
2010-12-15  6:46       ` Thierry Volpiatto
2010-12-16  1:15         ` Chong Yidong
2010-12-16  8:03           ` Thierry Volpiatto
2010-12-16 17:35             ` Eli Zaretskii
2010-12-16 18:07               ` Thierry Volpiatto
2010-12-16 18:10                 ` Eli Zaretskii
2010-12-16 18:43                   ` Thierry Volpiatto
2010-12-16 19:25                     ` Eli Zaretskii
2010-12-16 19:36                       ` Thierry Volpiatto
2010-12-18  7:24                       ` Thierry Volpiatto
2010-12-18  9:16 ` Thierry Volpiatto
2010-12-18 10:08   ` Eli Zaretskii
2010-12-21 11:34     ` Thierry Volpiatto
2010-12-28 13:14     ` Thierry Volpiatto

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=874odecgj9.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=7098@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /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).