public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	patsmith@pobox.com
Subject: Re: optimization/9015: bc segfaults when compiled with optimization
Date: Fri, 20 Dec 2002 19:20:00 -0000	[thread overview]
Message-ID: <20021221032050.28287.qmail@sources.redhat.com> (raw)

Synopsis: bc segfaults when compiled with optimization

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Fri Dec 20 19:20:49 2002
State-Changed-Why:
    It is very hard for us to reproduce a problem with such little
    information, since we don't really know what we're looking
    for. Sometimes such problems go away by moving to a different
    platform, and then we would not be able to reproduce it.
    Basically, a whole program is too large for us to find a
    bug in.
    
    What you could do is the following: try to run bc under
    a debugger and try to find out which function it crashes in
    by looking at a stacktrace after the crash happens. Then
    try to isolate the function in which this happens from
    the rest of the program and see whether you can come up
    with a small testcase from which we can work on. This
    would ideally just include the one function in which things
    happen, called from a dummy main function.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9015


             reply	other threads:[~2002-12-21  3:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 19:20 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03 19:46 bangerth
2003-01-03 19:46 Wolfgang Bangerth
2002-12-24 16:56 Patrick Smith
2002-12-20 22:06 Wolfgang Bangerth
2002-12-20 21:56 Patrick Smith
2002-12-19 20:46 patsmith

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=20021221032050.28287.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=patsmith@pobox.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. 
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).