public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9015: bc segfaults when compiled with optimization Date: Fri, 20 Dec 2002 22:06:00 -0000 [thread overview] Message-ID: <20021221060601.19103.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9015; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Patrick Smith <patsmith@pobox.com> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: optimization/9015: bc segfaults when compiled with optimization Date: Fri, 20 Dec 2002 23:56:56 -0600 (CST) > > 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. > > As mentioned in the original report, I think the problem is with the > function load_code in the source file included in the bug report. If > that function is compiled without optimization and the rest of bc is > optimized with -O2, the crash does not occur. > > I've already been the debugger and trying to create a small test program > route, without much luck. The crash occurs in another function (addbyte > in the same source file). > > I'm currently reading up on PowerPC assembly, so I can look at the > generated code for load_code and figure out if it's right or not. If > you want, I can send the .s file as well. Thanks for your effort. Basically, try to narrow it down as much as you can, and the let us know as much of the information you have. You may also want to check out whether recent snapshots of the compiler still show the same behavior -- maybe the bug was already fixed by someone. Thanks anyway! Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-21 6:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-20 22:06 Wolfgang 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 21:56 Patrick Smith 2002-12-20 19:20 bangerth 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=20021221060601.19103.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.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: linkBe 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).