On Wed, Aug 24, 2011 at 5:47 PM, Rob wrote: > This may be related to gdb crashing which happened before the last problem. > > If I do the following: > 1) debug a program > 2) load a few source files into buffers > 3) set a breakpoint > 4) kill gdb > 5) close a source file > 6) reset the breakpoint > > The breakpoint doesn't appear in any file. Maybe this is the same > problem and killing gdb messes up the list of buffers, and depending > on what files change the result is different?
Sorry, I do not understand 'reset the breakpoint'. After gdb has been killed, there are no breakpoints and the signs should have been removed by pyclewn. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
