Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=3754853
By: fabioz
Actually, the remote debugger is mostly for when you're running things without
the need for running it in debug mode, so, you just start the remote debugger
and when it hits that code it automatically 'switches' to debug mode. You should
be able to add breakpoints after switching to debug mode without problems.
Now, if you already start CP in debug mode from within Eclipse, that should
not be needed, as long as you set the tracing facility for each thread you create
(as I explained before), and breakpoints should work without problems. If they're
not working when you run things that way, it might be that for some reason the
filename that generated the module is lost in CP, but I find that very unlikely,
but as I haven't tested it, it might be the reason why that's happening.
If you believe that the breakpoints are missed because of something like that
you can report a bug, and we can do some things 'interactively', if you're willing
to do it, so, I'll pass you the changes, and you do them in your environment,
so that we can evaluate toghether what's happening.
Cheers,
Fabio
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=293649
|
