Comment 7 for bug 891970

In order to install gdb to debug msp430 I encountered some conflicts between gdb and gdb-msp430:

sudo dpkg -i --force-overwrite gdb_7.3-0ubuntu2_i386.deb
(Reading database ... 184431 files and directories currently installed.)
Unpacking gdb (from gdb_7.3-0ubuntu2_i386.deb) ...
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/gdb/python/gdb/__init__.py', which is also in package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/gdb/python/gdb/types.py', which is also in package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/gdb/python/gdb/printing.py', which is also in package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/gdb/python/gdb/command/__init__.py', which is also in package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/gdb/python/gdb/command/pretty_printers.py', which is also in package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
Setting up gdb (7.3-0ubuntu2) ...
Processing triggers for man-db ...

For now, gdb reports "no debugging symbols found" in the case of msp430-gdb which probably means I ought to recompile the package with -g. I suppose that this is what Andrzej Bieniek did to produce the stack trace above.