On Wed, Aug 31, 2011 at 3:07 PM, Rob wrote: > Thanks for the quick reply. Using the new pyclewn 1.7.py2 I have > had a problem where no breakpoint signs appear. In this case gdb > did not die, but I had first created a 'catch throw'. Clearing the > catch fixed the problem (see attachment, I have removed some lines > at [snip]). I'm not sure if this is related to the previous > problem. > > > 1) "catch throw" > 2) start program > 3) interrupt > > 4) set a breakpoint (console output and list bp shows it is set, but > no sign appears) > 5) delete catch point (sign appears)
This is a new bug, not related to the previous one. Gdb sets the catchpoints as being of type 'catchpoint'. For example 'catch syscall' will create a new entry of type 'catchpoint' in the breakpoint table, printed by 'info breakpoints'. This is fine with pyclewn. But there are two catchpoints that are typed by gdb as 'breakpoint' instead of 'catchpoint': the 'catch' and 'throw' catchpoints. This confuses pyclewn. I will fix it soon. Thanks for the bug report. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
