all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Halley <rthalley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 14587@debbugs.gnu.org
Subject: bug#14587: Segfault compiling cedet/srecode/texi.el during "make bootstrap"
Date: Fri, 14 Jun 2013 10:44:54 +0100	[thread overview]
Message-ID: <9D5CC0C0-3318-4885-97FC-ACF28B488FDF@gmail.com> (raw)
In-Reply-To: <51BA046A.3000709@cs.ucla.edu>


On Jun 13, 2013, at 6:42 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:

> On 06/13/13 10:36, Bob Halley wrote:
>> I tried that, and unfortunately the problem does not occur when compiled -O0.
> 
> How about configure with --enable-checking -- do you
> still get the same symptoms, or (hope, hope) do you get
> an assertion failure?  Also, for better debugging you might
> try CFLAGS='-g3 -O2 -fno-crossjumping' instead of plain -O2.

I did this, but the problem did not occur.  Getting suspicious, I tried a build on head with exactly the configuration that was failing for me before, and it no longer fails.  But, if I check out the tag after the cedet integration that I mentioned in my bug report, it still does fail.  So, something changed between the time I reported the bug and head that either fixes the problem or obscures it again :)

If you want to declare victory, that's OK with me, but I'm a little curious still so I'll try doing a build with the configuration you suggested against a version that fails. I will report if anything interesting happens.

/Bob






  reply	other threads:[~2013-06-14  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  7:42 bug#14587: Segfault compiling cedet/srecode/texi.el during "make bootstrap" Bob Halley
2013-06-13 17:14 ` Paul Eggert
2013-06-13 17:36   ` Bob Halley
2013-06-13 17:42     ` Paul Eggert
2013-06-14  9:44       ` Bob Halley [this message]
2013-06-14 15:49         ` Paul Eggert
2013-06-14 16:03           ` Bob Halley
2013-06-14 17:08             ` Paul Eggert
2013-06-14 12:21       ` Bob Halley

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=9D5CC0C0-3318-4885-97FC-ACF28B488FDF@gmail.com \
    --to=rthalley@gmail.com \
    --cc=14587@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.