| Curiously enough, after typing RUN and breaking at the breakpoint, the GUI
can now set the BPT even though it is sending EXACTLY the same string as
before...
$ set break in routine "gem_xx_compile(simple_gem_cp_context&)" in file
/usr/lusers/brett/project_exx/cpri-97-01-16/src/edg-dcg/compile.cxx
|
|
Bevin,
The string that you see in the $ set break command is not really the string
that is sent to the engine by the GUI.
The ladebug command that actually gets executed would be:
(ladebug) when in
"/usr/lusers/brett/project_exx/cpri-97-01-16/src/edg-dcg/compile.cxx"`gem_xx_com
pile(simple_gem_cp_context&) {stop}
If you type this command at the ladebug prompt, does it set the breakpoint ??
There are several scenarios where ladebug is not able to set the breakpoints,
if you fully qualify the breakpoint locations (as done here). This probably
due to invisibility of certain components - like the type in signature.
The reason you were able to set the breakpoint after being in that routine
was that probably now the type is visible.
Can I get the pointer to the binary to investigate further ??
thanks
shamim
|