This patch will make the `modules' command succeeed.
Later requesting the specific `gdb' module will cause:

help> gdb
problem in gdb - <type 'exceptions.AttributeError'>: 'module' object has
no attribute 'Command'

I think this is right in general, a single broken module should not
abort the whole modules traversal.


Another issues is why the `gdb' module fails: It expects the bindings
inside the native `/usr/bin/gdb' process to exist.  Should it just
silently skip its functions if no `/usr/bin/gdb' binding is found?  Or
should these gdb modules be located outside of `/usr/lib*/python2.x'?
There are already some glue python modules
in `/usr/share/gdb/auto-load/'.  Thanks for advice.