unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.6.3 documentation installation problem, Solaris 8, gcc 3.2.1 {PS}
Date: 05 Feb 2003 16:33:32 +0100	[thread overview]
Message-ID: <87lm0ud9o3.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200302051502.h15F2N223815@europa.research.att.com>

Andrew Koenig <ark@research.att.com> writes:

> I was going to suggest a binary-search approach to finding the
> problem, but of course that might not work if the optimization problem
> shows up in more than one translation unit.  But what should work is
> to compile everything with -O0, then recompiling source files one at a
> time with -O1 until the failure reappears.

Yeah, another approach is to just run the thing in the debugger and
trace the segfault back to where the optimization screwed us.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


  reply	other threads:[~2003-02-05 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03  4:26 guile 1.6.3 documentation installation problem, Solaris 8, gcc 3.2.1 {PS} Andrew Koenig
2003-02-03 19:31 ` Marius Vollmer
2003-02-03 20:29   ` Andrew Koenig
2003-02-04 14:11     ` Marius Vollmer
2003-02-04 20:14       ` Andrew Koenig
2003-02-05 13:22         ` Marius Vollmer
2003-02-05 15:02           ` Andrew Koenig
2003-02-05 15:33             ` Marius Vollmer [this message]
2003-02-05 15:35               ` Andrew Koenig
2003-02-04 20:55       ` Andrew Koenig

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/guile/

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

  git send-email \
    --in-reply-to=87lm0ud9o3.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --cc=bug-guile@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.
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).