Remote Debugging is broken

Would it be possible to fix remote debugging. When using shared memory
transport it would not connect to my running JVM and show error something
like "Can not connect Shared memory on address 5005". It seems to me it is
using IP Port instead of shared mem address I provide. Oh well back to
Ariadna


6 comments
Comment actions Permalink

Fixed this, thanks,
BTW why are you using shmem instead of socket? Socket transport seems to be more stable and I haven't noticed any performance
differences.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


"Alex Roytman" <nospam@hello.world> wrote in message news:cvdggt$2rk$1@is.intellij.net...

Would it be possible to fix remote debugging. When using shared memory transport it would not connect to my running JVM and show
error something like "Can not connect Shared memory on address 5005". It seems to me it is using IP Port instead of shared mem
address I provide. Oh well back to Ariadna



0
Comment actions Permalink

I suppose I'm just retarded, but how could remote debugging possibly work with shmem?

0
Comment actions Permalink

If both processes are located on the same machine

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

"Patrik Andersson" <pandersson@gmail.com> wrote in message news:22065160.1109084135609.JavaMail.itn@is.intellij.net...
>I suppose I'm just retarded, but how could remote debugging possibly work with shmem?


0
Comment actions Permalink

Thank you very much Eugene,

At some poin in the distant past it worked faster for me so I got used to it
plus tomcat comes configured with shared mem debugging so I do not need to
remember to change startup scripts every time I upgrade. I will give sockets
a try though

Thanks

Alex


"Eugene Zhuravlev (JetBrains)" <jeka@intellij.com> wrote in message
news:cvfg17$i4p$1@is.intellij.net...

Fixed this, thanks,
BTW why are you using shmem instead of socket? Socket transport seems to
be more stable and I haven't noticed any performance differences.

>

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

>
>

"Alex Roytman" <nospam@hello.world> wrote in message
news:cvdggt$2rk$1@is.intellij.net...

>> Would it be possible to fix remote debugging. When using shared memory
>> transport it would not connect to my running JVM and show error something
>> like "Can not connect Shared memory on address 5005". It seems to me it
>> is using IP Port instead of shared mem address I provide. Oh well back to
>> Ariadna
>>
>



0
Comment actions Permalink

I have tried tomcat (4.1.34) remote debugging with very little success. It stops fine at the breakpoint but when I try to look into local/stack vars etc. it continously runs out of memory - I have tried as much as 700MB for IntelliJ and still no luck.

What I have observed is that the point where I stop - if the variables to be displayed (instance varibles + method params + local vars + class variables) have a huge object graph that can result into huge toString, then I have this problem. This has forced me to use souts quite often.

This does not happen in the release version - just in the EAP.

0
Comment actions Permalink

Does it help if you disable showing objects as toString() and collection renderers?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


"Vinay Moharil" <vmohar98@yahoo.com> wrote in message news:8655498.1109102229861.JavaMail.itn@is.intellij.net...
>I have tried tomcat (4.1.34) remote debugging with very little success. It stops fine at the breakpoint but when I try to look into
>local/stack vars etc. it continously runs out of memory - I have tried as much as 700MB for IntelliJ and still no luck.
>

What I have observed is that the point where I stop - if the variables to be displayed (instance varibles + method params + local
vars + class variables) have a huge object graph that can result into huge toString, then I have this problem. This has forced me
to use souts quite often.

>

This does not happen in the release version - just in the EAP.



0

Please sign in to leave a comment.