System: NT4 SP4 JDE: jde-2.1.6beta12 Project and .emacs files on request if necessary, but I think this one is buried in the jde lisp somewhere... In brief, when I selected Trace method entry, entered values in the form, and selected [Ok], the class inclusion and class exclusion patterns were generated incorrectly in the debugger command line. Entering the following in the Trace method Entry form, and selecting [Ok]: <THE_FORM> Trace method entry Thread restriction: Restrict trace to the specified thread. Thread Suspension Policy: [Options] none Specify which thread to suspend on method entry or exit. Class inclusion filters: [INS] [INS] [DEL] Filter: com.aviatis.* Regular expressions that specify classes whose methods should be traced. Class exclusion filters: [INS] [INS] [DEL] Filter: java.* Regular expressions that specify classes whose methods should not be traced. [Ok][Cancel] </THE_FORM> ...resulted in the following fragement in the JDEbug buffer: <THE_BUFFER_FRAGMENT> JDE> 1 2 trace_methods entry -sp none -cf "com.aviatis.*" -cef "com.aviatis.*" (jde-dbo-command-result 2 0) </THE_BUFFER_FRAGMENT> When I entered and selected just an inclusion pattern value, the same incorrect pattern was generated, i.e., 'JDE> 1 2 trace_methods entry -sp none -cf "com.aviatis.*" -cef "com.aviatis.*" ' Any hints patching this up? I really need the trace capability.... ------------------------------------------------------------------------ Joel Wormer e-mail: [EMAIL PROTECTED], ph:+1(408)557-6719 Aviatis Corp. 650 Saratoga Ave. San Jose, CA 95129, USA ------------------------------------------------------------------------
