They are not insurmontable problems. But you will still see things like this:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/66510 The point being that with a newish GDB (the current mingw GDB is still 5.x) there's no need for such tedious tricks, since it handles pending breakpoints fine. The additional trick I use for debugging plain non-debug python is to use symbol-file to load some arbitrary symbols, so GDB will not complain about breakpoints. steve d. On Apr 15, 2:41 am, Paul Rubin <http://[EMAIL PROTECTED]> wrote: > SteveD <[EMAIL PROTECTED]> writes: > > pgdb.zip is an addition to scite-debug, which adds source debugging to > > the popular SciTE programmer's editor. ... > > I know the FAQ says that this is not possible, but the FAQ is somewhat > > outdated. GDB is quite happy with pending breakpoints to unresolved > > libraries, but you have to reassure it. > > I'm not sure what FAQ or what is supposed to be impossible but > I've used gdb in the past to debug python extensions without > running into insurmountable problems that I remember. -- http://mail.python.org/mailman/listinfo/python-list
