public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32853] [4.3 regression] failing libjava testcases
Date: Fri, 27 Jul 2007 18:20:00 -0000 [thread overview]
Message-ID: <20070727181949.4364.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32853-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from debian-gcc at lists dot debian dot org 2007-07-27 18:19 -------
Reopened:
http://lists.debian.org/debian-glibc/2007/07/msg00346.html:
On Thu, Jul 26, 2007 at 09:16:00PM +0000, aurel32@alioth.debian.org wrote:
> +2006-11-30 Jan Kratochvil <jan.kratochvil@redhat.com>
> +
> + * sysdeps/unix/sysv/linux/x86_64/clone.S: Provide CFI for the outermost
> + `clone' function to ensure proper unwinding stop of gdb.
I don't get it. The changelog entry is for _adding_ the directives
and matches the changelog entry in glibc HEAD. This patch removes
them.
If removing them makes anything better then it's got to be a bug in
java's unwinder.
--
Daniel Jacobowitz
CodeSourcery
--
debian-gcc at lists dot debian dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32853
next prev parent reply other threads:[~2007-07-27 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 15:18 [Bug java/32853] New: " debian-gcc at lists dot debian dot org
2007-07-22 19:33 ` [Bug target/32853] " pinskia at gcc dot gnu dot org
2007-07-24 7:21 ` debian-gcc at lists dot debian dot org
2007-07-27 16:57 ` debian-gcc at lists dot debian dot org
2007-07-27 18:20 ` debian-gcc at lists dot debian dot org [this message]
2007-07-28 0:01 ` daney at gcc dot gnu dot org
2007-07-28 0:21 ` pinskia at gcc dot gnu dot org
2007-08-10 0:51 ` mmitchel at gcc dot gnu dot org
2007-08-10 6:26 ` debian-gcc at lists dot debian dot org
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=20070727181949.4364.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).