public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Java Patch List <java-patches@gcc.gnu.org>
Subject: Re: [RFC/JVMTI] GetMethodDeclaringClass
Date: Fri, 27 Oct 2006 10:17:00 -0000	[thread overview]
Message-ID: <17729.56513.133225.251768@zebedee.pink> (raw)
In-Reply-To: <45414D77.1020109@redhat.com>

Keith Seitz writes:
 > Andrew Haley wrote:
 > >  > [It would be really appreciated if someone with access to
 > >  > ppc64-linux or somesuch could double-check for a failure in the
 > >  > stack tracing tests in lang.exp.]
 > > 
 > > I suggest you ask Andrew Overholt for access to his ppc64 box.
 > 
 > Okay, I finally found a machine to test this on. I tried three test runs:
 > 
 > 1) Virgin SVN HEAD
 > 2) #1 + my patch
 > 3) #2 - the "filter out interpreted classes" (to make sure that the bug 
 > was tested)
 > 
 > #1 & #2 were the same. #3 showed backtrace problems. So I guess we can 
 > conclude that my patch does not cause any regressions.

OK, excellent.  Please commit.

Andrew.

  reply	other threads:[~2006-10-27 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 18:09 Keith Seitz
2006-10-17 18:14 ` Andrew Haley
2006-10-17 19:05   ` Andrew Haley
2006-10-17 18:42     ` Keith Seitz
2006-10-17 18:53       ` Andrew Haley
2006-10-18 23:04         ` Keith Seitz
2006-10-19  8:22           ` Andrew Haley
2006-10-23 20:50             ` Keith Seitz
2006-10-24  6:36               ` Andrew Haley
2006-10-27  0:06                 ` Keith Seitz
2006-10-27 10:17                   ` Andrew Haley [this message]
2006-10-28  2:16                     ` Keith Seitz
2006-10-17 18:23 ` Per Bothner

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=17729.56513.133225.251768@zebedee.pink \
    --to=aph@redhat.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=keiths@redhat.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).