I am trying to set up a breakpoint in one of the source files . When I set the breakpoint it says "Breakpoint deferred until a shared library containing ":646" is loaded.
When i try and run the program the breakpoint is never reached in the debugger.
So i tried using printf and I put a printf statement in the same file at the same line number and re-compiled the binaries . Now I can see the printf statements being displayed on the console, but the breakpoint is still never achieved by the debugger.
Re: Breakpoint deferred and never reached in debugger
Adarsh, As per my understanding it is a shared library code where you are trying to put the breakpoint . This library loads and executes but the breakpoint stays deferred and so is not hit. Let me know if I am wrong somewhere.
As Dennis suggested you can try different ways of putting the breakpoint. Try list command to display the these source lines during the debugger session. Try setting catch point "catch load " at the starting of the session so as to know when that particular library is getting loaded. Once this catch point is hit gdb will stop and you can try and put your breakpoint now it should no more be deferred. If nothing works send us the session o/p with all the details and if possible a test-case so that we can reproduce it at our end. Send us at wdb-help@cup.hp.com
Re: Breakpoint deferred and never reached in debugger
I think I know the problem now , when i load the exe in the debugger , there seesm to be a fork happening and maybe the file that I want to debug is getting loaded in the other process .
Re: Breakpoint deferred and never reached in debugger
WDB can debug only one process at a time either child or parent. So "set follow-fork-mode" as suggested by Dennis is to set the behavior of WDB after the application forks a new process.
