Go to main content
Oracle® Developer Studio 12.6: Debugging a Program with dbx

Exit Print View

Updated: June 2017
 
 

call Command

In native mode, the call command calls a procedure. In Java mode, the call command calls a method.

You can also use the call command to call a function. To display the return value use the print command.

Occasionally the called function hits a breakpoint. You can choose to continue using the cont command or abort the call by using pop -c. The latter method is useful also if the called function causes a segmentation fault.

Native Mode Syntax

call [–lang language] [–resumeone] [–m] [+m] procedure ([parameters])

where:

language is the language of the called procedure.

procedure is the name of the procedure.

parameters are the procedure’s parameters.

–lang specifies the language of the called procedure and tells dbx to use the calling conventions of the specified language. This option is useful when the procedure being called was compiled without debugging information and dbx does not know how to pass parameters.

–resumeone resumes only one thread when the procedure is called. For more information, see Resuming Execution.

–m specifies that macro expansion be applied to the procedure and parameters when the dbxenv variable macro_expand is set to off.

+m specifies that macro expansion be skipped when the dbxenv variable macro_expand is set to on.

Java Mode Syntax

call [class-name.|object-name.] method-name ([parameters])

where:

class-name is the name of a Java class. You can use either of the following:

  • The package path using a period (.) as a qualifier; for example, test1.extra.T1.Inner

  • The full path name preceded by a pound sign (#) and using slash (/) and dollar sign ($) as qualifiers. For example, #test1/extra/T1$Inner. Enclose class-name in quotation marks if you use the $ qualifier.

object-name is the name of a Java object.

method-name is the name of a Java method.

parameters are the method’s parameters.