This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/9015: bc segfaults when compiled with optimization
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, patsmith at pobox dot com
- Date: 21 Dec 2002 03:20:50 -0000
- Subject: Re: optimization/9015: bc segfaults when compiled with optimization
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, patsmith at pobox dot com, gcc-gnats at gcc dot gnu dot org
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