In a program, the same name might refer to different types of program entities and occur in many scopes. The dbx whereis command lists the fully qualified name, and hence the location, of all symbols of that name. The dbx which command tells you which occurrence of a symbol dbx would use if you give that name in an expression.
To print a list of all the occurrences of a specified symbol, use whereis symbol, where symbol can be any user-defined identifier. For example:
(dbx) whereis table forward: `Blocks`block-draw.cc`table function: `Blocks`block.cc`table::table(char*, int, int, const point&) class: `Blocks`block.cc`table class: `Blocks`main.cc`table variable: `libc.so.1`hsearch.c`table
The output includes the name of the loadable objects where the program defines symbol, as well as its entity type: class, function, or variable.
Because information from the dbx symbol table is read in as it is needed, the whereis command registers only occurrences of a symbol that are already loaded. As a debugging session gets longer, the list of occurrences can grow. For more information, see Debugging Information in Object Files and Executables.
The which command tells you which symbol with a given name dbx uses if you specify that name without fully qualifying it in an expression. For example:
(dbx) func wedge::wedge(char*, int, int, const point&, load-bearing-block*) (dbx) which draw `block-draw.cc`wedge::draw(unsigned long)
If a specified symbol name is not in a local scope, the which command searches for the first occurrence of the symbol along the scope resolution search path. If which finds the name, it reports the fully qualified name.
If at any place along the search path the search finds multiple occurrences of symbol at the same scope level, dbx prints a message in the command pane reporting the ambiguity.
(dbx) which fid More than one identifier `fid’. Select one of the following: 0) Cancel 1) `example`file1.c`fid 2) `example`file2.c`fid
dbx shows the overload display, listing the ambiguous symbols names. In the context of the which command, choosing from the list of occurrences does not affect the state of dbx or the program. Whichever occurrence you choose, dbx echoes the name.
The which command gives you a preview of what happens if you make symbol (in this example, block) an argument of a command that must operate on symbol (for example, a print command). In the case of ambiguous names, the overload display list indicates that dbx does not yet register which occurrence of two or more names it uses. dbx lists the possibilities and waits for you to choose one.
When you issue a debugging command that contains an expression, the symbols in the expression are looked up in the following order. dbx resolves the symbols as the compiler would at the current visiting scope.
Within the scope of the current function using the current visiting scope If the program is stopped in a nested block, dbx searches within that block, then in the scope of all enclosing blocks.
For C++ only: class members of the current function's class and its base class.
For C++ only: the current name space.
The parameters of the current function.
The immediately enclosing module, which is generally, the file containing the current function.
Symbols that were made private to this shared library or executable. These symbols can be created using linker scoping.
Global symbols for the main program, and then for shared libraries.
If none of the above searches are successful, dbx assumes you are referencing a private, or file static, variable or function in another file. dbx optionally searches for a file static symbol in every compilation unit depending on the value of the dbxenv setting scope-look-aside.
dbx uses whichever occurrence of the symbol it first finds along this search path. If dbx cannot find the symbol, it reports an error.
To relax the scope lookup rules for static symbols and C++ member functions, set the dbxenv variable scope-look-aside to on:
dbxenv scope-look-aside on
You can also use the “double backquote” prefix:
stop in ``func4 func4 may be static and not in scope
If the dbxenv variable scope-look-aside is set to on, dbx looks for the following:
Static variables defined in other files if not found in current scope. Files from libraries in /usr/lib are not searched.
C++ member functions without class qualification.
Instantiations of C++ inline member functions in other files if a member function is not instantiated in current file.
The which command tells you which symbol dbx would choose. In the case of ambiguous names, the overload display list indicates that dbx has not yet determined which occurrence of two or more names it would use. dbx lists the possibilities and waits for you to choose one.