This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/13158] bad unwind info as a result of sibcall
- From: "wilson at specifixinc dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 May 2004 08:40:34 -0000
- Subject: [Bug target/13158] bad unwind info as a result of sibcall
- References: <20031122025223.13158.davidm@hpl.hp.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From wilson at specifixinc dot com 2004-05-14 08:40 -------
Subject: Re: bad unwind info as a result of sibcall
On Wed, 2004-05-12 at 21:25, davidm at hpl dot hp dot com wrote:
> I tested the patch with the above "bug.c" routine when run under libunwind's
> "test-ptrace" program (which single-steps through the program, unwinding the
> stack at each point). This test-case now succeeds, so the basics look good.
This seems reasonable to me. I tried testing the patch, and ended up
with 2 extra libjava failures. I tried rerunning the libjava
testsuites, and the extra failures were repeatable. I think I need to
look at this. I am not exactly sure what the libjava testsuite was
trying to do. It byte compiled a file to get a class file, and then
executed it? I need to figure out more about what the libjava testsuite
was doing before I can look into this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13158