| Remote debugging, shared memory transport [message #199140] |
Mon, 21 March 2005 11:23  |
Eclipse User |
|
|
|
Originally posted by: roman.kishchenko.appiq.com
Hi,
I am trying to setup remote debugging configuration. However, JDWP socket
listener does not seem to get started in the remote process (it happens on
one of the Windows machines I have, I am yet to find out why). Switching
to shared memory transport works. I tried it with jdb and IDEA, the later
editor allows this configuration. However, in Eclipse 3.0.1 the only
option available is "Standard (Socket Attach)". How can remote debugging
with shared memory transport be configured?
Roman
|
|
|
|
| Re: Remote debugging, shared memory transport [message #199285 is a reply to message #199239] |
Wed, 23 March 2005 11:45  |
| Eclipse User |
|
|
|
Originally posted by: roman.kishchenko.appiq.com
I used very simple configuration, starting JBoss server (4.0) (by
uncommenting JPDA options) in the run script and attaching from Eclipse on
the same machine. This morning, I double checked the problem and it was
still occuring as I described before with shared memory transport working
fine. Before posting a follow-up message with configuration information
and all I decided to try a different VM (1.5.0_02), 1.4.2_04 was the one I
used before, as 1.5 is the VM version that worked on a different Windows
machine. Socket transport with 1.5 worked fine! What is more bizzare is
that on 1.4 it also started working. I know it sounds strange and if
having been told the same I would have my doubts but this is what I have
so far. I will try to find out more plausible explanation.
(While looking at this I found some vague references to the problem on
Windows with comments such on this feedback post to the article about
debugging in Eclipse:
http://sys-con.com/story/feedback.cfm?storyid=44918.)
|
|
|
Powered by
FUDForum. Page generated in 0.02611 seconds
Home