Bug 178820 - can NOT do the debug and type program line by line!
Summary: can NOT do the debug and type program line by line!
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
(Show other bugs)
Version: 4
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact:
URL: https://bugs.eclipse.org/bugs/show_bu...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-24 16:57 UTC by zhuge
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-24 17:03:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description zhuge 2006-01-24 16:57:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1

Description of problem:
can NOT do the debug and type program line by line!

Please see the following bug I reported to Eclipse:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=123118

 or the bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=123402

Version-Release number of selected component (if applicable):
kernel-2.6.14

How reproducible:
Always

Steps to Reproduce:
1. see ----   https://bugs.eclipse.org/bugs/show_bug.cgi?id=123402
2. or see ----- https://bugs.eclipse.org/bugs/show_bug.cgi?id=123118
3.
  

Actual Results:  Cannt to connect to VM

Expected Results:  Cannt to connect to VM

Additional info:

From the following .log's message, I can know the build of Eclipse on my system is 3.1.1.

!SESSION 2006-01-24 02:42:53.201
-----------------------------------------------
eclipse.buildId=M20050929-0840
java.fullversion=GNU libgcj 4.0.2 20051125 (Red Hat 4.0.2-8)
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=zh_CN
Command-line arguments:  -os linux -ws gtk -arch x86

!ENTRY org.eclipse.jdt.launching 4 120 2006-01-24 02:46:48.558
!MESSAGE Cannot connect to VM
!STACK 0
com.sun.jdi.connect.TransportTimeoutException
   at
org.eclipse.jdi.internal.connect.SocketTransportService.accept(com.sun.jdi.connect.spi.TransportService$ListenKey,
long, long) (/usr/lib/gcj/eclipse/jdimodel.jar.so)
   at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(long, long)
(/usr/lib/gcj/eclipse/jdimodel.jar.so)
   at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(java.util.Map)
(/usr/lib/gcj/eclipse/jdimodel.jar.so)
   at
org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run()
(/usr/lib/gcj/eclipse/org.eclipse.jdt.launching_3.1.0.jar.so)
   at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0)

Comment 1 Andrew Overholt 2006-01-24 17:03:31 UTC
There is no JDWP support (what Eclipse uses for debugging java bytecode) in gij
yet.  It is being worked on.

Comment 2 zhuge 2006-01-24 17:20:48 UTC
I suggest that you should fixed the bug through contacting with Eclipse.

Comment 3 Andrew Overholt 2006-01-24 17:22:58 UTC
(In reply to comment #2)
> I suggest that you should fixed the bug through contacting with Eclipse.

It's not a matter of working with the eclipse.org people.  It's just a matter of
getting JDWP support.  It's being worked on.

Comment 4 zhuge 2006-01-24 17:37:53 UTC
I suggest that you should fixed the bug through contacting with Eclipse.


Note You need to log in before you can comment on or make changes to this bug.