UG NX 二次开发 调试 debug的使用步骤

admin

' O$ `. Z$ B$ S: D9 U
8 g, @5 ^$ @- D' i/ u) _/ v
" \" j/ u" s2 i# s/ E7 s) I

DebUGging and Running
  
0 n- l: [5 R" z' P$ D If the project is an internal Open C application (DLL), the following steps must be performed to associate the NX executable with the project. If these steps are not performed, the application cannot be executed or debugged from the Visual C++ environment. These steps do not apply to external Open C applications (EXEs).
5 g; r! m% C& O5 s& x# G; o4 U! \2 z  
Step 1 Determine the location of the NX executable ugraf.exe.
  
Go to the Windows "Start" menu and select "Settings->Control Panel". Double-click the "System" icon. Click the "Environment" tab on the resulting "System Properties" dialog. In the "System Variables" list scroll down until you find a variable named "UGII_ROOT_DIR". The value associated with this variable is the directory path to the "ugraf.exe" executable. Select the "UGII_ROOT_DIR" variable. Highlight the complete path in the "Value" field at the bottom of the dialog and copy it to the clipboard.
& \; S6 [$ o% a' v' l, K4 H  
6 a( x0 Q) Y+ v4 | Step 2 Associate the NX executable with your project.
/ K8 j! }; I, P: z/ G' x- w, Z& D  
! X# ]' A/ D2 ]2 u- f. f From within Visual C++, select the "Project->Settings" menu item and select the "Debug" tab on the resulting "Project Settings" dialog. Notice that the "Executable for debug session:" field is empty. Place the cursor in this field and then type or paste the path determined in the first step, followed by "\ugraf.exe". For example, if the value of "UGII_ROOT_DIR" were "C:\ugnx50\ugii" then you would enter: C:\ugnx50\ugii\ugraf.exe. You may also browse for the executable file by clicking the arrow button to the right of the "Executable for debug session:" field.
( _. l2 d# H3 E* O) w  
" |4 |. k4 a. S0 U Step 3 Set the working directory.
) C6 S6 {! W8 b  I! U" {  
The "Working directory:" field on the "Project Settings" dialog specifies the directory from which Visual C++ runs NX. A common convention is to use "C:\TEMP" for the working directory.
  
6 {$ i- Z8 _" M1 k$ A Step 4 Set the NX program arguments (optional)
" T; j% o) t9 @; ?" z# a4 p& j  
You may set any NX program arguments you require by entering them in the "Program arguments:" field on the "Project Settings" dialog. The syntax is exactly the same as the command-line syntax for starting NX.
  
. L5 S5 R1 C+ q4 Z/ Y( W) r Step 6 Run the Application
+ K" P# A$ r0 w9 A8 v  
Click "OK" in the "Project Settings" dialog and then run or debug the application as you would normally from Visual C++. NX is started each time the project is executed. You are free to place breakpoints in your Open C application just as you would in any other application. It may take a few moments for NX to appear because Visual C++ is searching for debug symbols in the NX DLLs, so be patient.
  

Print statements

Since NX is a native Windows application, there is no console started up automatically. Therefore using a printf to print to stdout will not work. If you want to use printf statements to debug your internal Open C application, you must add the following code to your internal Open C API function:
! B1 m% V* x; u, X  
#include <windows.h>
1 e. w$ d( W7 S2 A! \8 x #include <fstream.h>
#include <stdio.h>
4 n8 B4 X% q* [1 o- B ...
: K3 N- b* K) Y1 V% Z2 p% d FILE *fp;
...

2 ?$ R$ S  b. t /* allocate console window conout$ */
$ J5 ~+ r6 K& l% h! m) L+ j8 T2 Z. V# @AllocConsole();
3 {  P; q5 {' h5 |* j: D5 q& v /* reopen stdout on conout$ for fprintf and printf */
fp = freopen("conout$", "w", stdout);
& ]2 q# Z8 o9 M- U4 O2 m# Q  
* a' z2 `+ e( z2 J# z4 C5 p This will create a console window and attach it to stdout so that printf and fprintf will work.
  

$ U* U) ?* c6 G* K+ P. ^7 |& ?9 Y