public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: keiths@redhat.com
Cc: GCJ-patches <java-patches@gcc.gnu.org>
Subject: jdwp build failure
Date: Wed, 21 Feb 2007 12:46:00 -0000	[thread overview]
Message-ID: <45DC3F0A.2040309@gmx.ch> (raw)
In-Reply-To: <45D6BD39.4070303@gmx.ch>

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

Hey all

I pointed this out already last week but maybe it slipped under or got 
forgotten (or I'm just too impatient):
jdwp currently causes a build error since "OUT" seems to be reserved for 
something else or whatever. In any case, I just renamed it to OUTT and 
the build works again.

Keith, this is your field as far as I noticed on the mailinglist. Can 
you give it a meaningful name and commit?


thanks
Marco

[-- Attachment #2: jdwp-mingw-examplefix.txt --]
[-- Type: text/plain, Size: 986 bytes --]

Index: gnu/classpath/jdwp/JdwpConstants$StepDepth.h
===================================================================
--- gnu/classpath/jdwp/JdwpConstants$StepDepth.h	(revision 122072)
+++ gnu/classpath/jdwp/JdwpConstants$StepDepth.h	(working copy)
@@ -28,7 +28,7 @@
   JdwpConstants$StepDepth();
   static const jint INTO = 0;
   static const jint OVER = 1;
-  static const jint OUT = 2;
+  static const jint OUTT = 2;
   static ::java::lang::Class class$;
 };
 
Index: gnu/classpath/jdwp/natVMVirtualMachine.cc
===================================================================
--- gnu/classpath/jdwp/natVMVirtualMachine.cc	(revision 122072)
+++ gnu/classpath/jdwp/natVMVirtualMachine.cc	(working copy)
@@ -889,7 +889,7 @@
 	    }
 	  break;
 
-	case JdwpConstants$StepDepth::OUT:
+	case JdwpConstants$StepDepth::OUTT:
 	  // All we need to do is check the stack depth
 	  if (sinfo->stack_depth > frame->depth ())
 	    handle_single_step (env, sinfo, thread, method, location);


  parent reply	other threads:[~2007-02-21 12:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 21:11 FYI: 2 patches for RH 4.1 branch Tom Tromey
2007-02-17  1:53 ` Mohan Embar
2007-02-17  8:31   ` Marco Trudel
2007-02-17 21:35     ` Marco Trudel
2007-02-17 23:08       ` Mohan Embar
2007-02-18 10:54       ` Marco Trudel
2007-02-19 13:10       ` Mohan Embar
2007-02-19 13:21         ` Marco Trudel
2007-02-21 12:46     ` Marco Trudel [this message]
2007-02-21 18:05       ` jdwp build failure Mohan Embar
2007-02-22  2:04         ` Tom Tromey
2007-02-22  2:37           ` Mohan Embar
2007-02-22  8:10             ` Marco Trudel
2007-02-22  8:12 Danny Smith
2007-02-22  8:21 ` Marco Trudel

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=45DC3F0A.2040309@gmx.ch \
    --to=mtrudel@gmx.ch \
    --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).