gdb

Hi,

I am trying to debug a multithreaded application using gdb. I have put
a breakpoint in a function which will essentially be invoke by main
process and dlopen calls for each DSO opened by it. When I run it,
control stops at breakpoint when the code is invoked by main process.
Later when I try continue, threads start spawning but none of them
stops at the breakpoint.

Can anyone please suggest what could be the probable reason for this
problem?

Thanks and Regards
Bhawna
.

Relevant Pages

  • Re: [Patch 00/12] Hardware Breakpoint Interfaces
    ... after IPI and I will explain it below]. ... does a busy wait through cpu_relax) and should be safe to invoke ... The breakpoint handler would use the per-cpu instance which will remain ... CPU recomputing it whenever a kernel breakpoint is added or removed. ...
    (Linux-Kernel)
  • Re: Simple race condition that I cant solve.
    ... If I change that back to Invoke, ... BeginInvoke() (tested by putting a breakpoint in HandleFinished and seeing ... Prev by Date: ...
    (microsoft.public.dotnet.framework)
  • Re: Conflicting VB Code
    ... try setting a breakpoint in your macro and invoke it manually. ... Frank Kabel ...
    (microsoft.public.excel.programming)
  • Re: VBA debugger
    ... not possible to invoke the function from the debugger itself. ... Once invoked from the spreadsheet, with your breakpoint, I see that I ...
    (comp.lang.basic.visual.misc)
  • [PATCH 9/21] KGDB: This adds basic support to the MIPS architecture
    ... This patch also adds support for the rs232 early kgdb access for MIPS ... * To enable debugger support, ... * or error conditions to be properly intercepted and reported to gdb. ... a breakpoint needs to be generated to begin communication. ...
    (Linux-Kernel)