Bug 205169 - Debug can not be launched. Run can.
Summary: Debug can not be launched. Run can.
Status: RESOLVED DUPLICATE of bug 127158
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
: 205170 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-02 08:25 EDT by ottawalyli CLA
Modified: 2007-10-04 10:11 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ottawalyli CLA 2007-10-02 08:25:15 EDT 
Build ID: M20070921-1145

Steps To Reproduce:
1. In a linux box, launch eclipse 3.3
2. Run a program, worked.  Cancel it. 
3. Debug a program, did not work.


More information:
ERROR: transport error 202: gethostbyname: unknown host ["transport.c",L70]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L547]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
Fatal error: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)

Eclipse Platform

Version: 3.3.0
Build id: M20070921-1145
Comment 1 Remy Suen CLA 2007-10-02 18:06:31 EDT 
Could you provide more information like your JRE version?
http://wiki.eclipse.org/Graphical_Eclipse_FAQs#How_do_I_find_out_which_Java_runtime_environment_is_being_used_to_run_my_Eclipse.3F

Googling came up with this hit which seems to be identical to your problem:
http://forum.java.sun.com/thread.jspa?threadID=596305&messageID=3205741
Comment 2 Kevin McGuire CLA 2007-10-03 17:31:27 EDT 
*** Bug 205170 has been marked as a duplicate of this bug. ***
Comment 3 Darin Wright CLA 2007-10-03 21:40:19 EDT 
Does your hosts file map localhost properly? i.e.

127.0.0.1       127.0.0.1

@see bug 5163
Comment 4 Michael Rennie CLA 2007-10-04 10:11:46 EDT 

*** This bug has been marked as a duplicate of bug 127158 ***