At 01:19 PM 6/23/00 +0100, you wrote:
>System : WinNT4, JDE2.1.7, JDK1.3,
>
>I've the following directory structure in ClearCase:
>
>Drive
>|
>+-- A
>|
>+-- C
>|
>+-- ...
>
>C belongs to the root package ie. oracle. ...
>A belongs not the oracle root package ie. 3rdParty
>
>In the JDE environment I've (or think) all the .jar files and
>all the source files for debugging.
>
>The program main class lifes in C and loads prj.el in the root
>package. As long as I set my breakpoint in C everything goes
>smooth - no problem !!! But trying to set a breakpoint in a A
>method causes some problems :
>
>- The prj.el files is not picked up due to a error I mailed
> out earlier so I load it manually.
>- So the JDEbug menu appears and I set the breakpoint
>- I go to the IDE which was started in C and invoke a menu
> command which calls the whiched function in A.
>- ... nothing happens everything freezes and thats it.
> I've to kill all the processes using the TaskManager.
>
This could be related to the raise frame that other people have reported.
When the debuggee process hits a breakpoint, the JDE tries to bring the
Emacs window to the top of the windows stack on your desktop. This
apparently can create a lockup between Emacs and the GUI being debugged. A
workaround is to turn the raise-frame feature off. To do this, select
Preferences from the JDEbug menu and turn the variable
jde-bug-raise-frame-p off.
- Paul
>So here is my questions :
>
>- Can I have different prj.el files in debugg session, ie.
> are new pathes picked up?
No. The JDE turns off project file loading during debugging. This is to
ensure that jde-db-source-directories does not inadvertently reset as you
are stepping through code. There is really no need to reload project files
when you are stepping through code. You should remain in the environment
that you started when you started debugging.
- Paul
