Caveats for procedure calls
- Any breakpoints encountered during command window procedure invocation are handled as usual.
- Return values from procedures are not guaranteed to be correct if a breakpoint is encountered during a procedure call.
- If function prototype information is available, the debugger checks the function prototype and converts each argument expression to the proper type of the corresponding parameter. If it is not available, automatic promotion of arguments and detection of invalid arguments is not supported and you should ensure that function arguments specified are compatible with the function called.
- When evaluating a C expression, the debugger invokes any compiled function, with or without arguments, including both application and operating system functions. However, an OS function on the target system is only called if already linked into your program. You are responsible for linking any system calls that are called from the command line into the program.
- In C++, or any other language with inlined procedures, a procedure only inlined (so there is no stand-alone version of the procedure) may not be called.
- In C++, the expression evaluator is unable to disambiguate overloaded procedure names. In this case, a dialogue will prompt you to identify which function should be used.
- In C++, default arguments are not inserted.
- In C++, the class member operator(), the function call operator, and the new and delete operators are not supported.
Related topic:
Copyright © 1999, Green Hills Software. All rights
reserved.