Wesley <nisp...@gmail.com> writes: > ... > [root@localhost ~]# gdb python > GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) > This GDB was configured as "x86_64-redhat-linux-gnu". > Reading symbols from /usr/bin/python...Reading symbols from > /usr/lib/debug/usr/bin/python2.6.debug...done. > done. > (gdb) run > Starting program: /usr/bin/python > warning: the debug information found in > "/usr/lib/debug//usr/lib64/libpython2.6.so.1.0.debug" does not match > "/usr/lib64/libpython2.6.so.1.0" (CRC mismatch). > > warning: the debug information found in > "/usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug" does not match > "/usr/lib64/libpython2.6.so.1.0" (CRC mismatch).
This indicates that there is a problem between the executed code and the debug information. Apparently, they do not match. An installation problem might be the cause - maybe, a packaging problem. Have you not told us that you have build your own Python from source? Usually, such a Python would not reside under "/usr/bin" but more likely under "/usr/local/bin" (of course, doing special things, you can force a build from source to install unter "/usr/bin", but this usually is not advicable -- it is potentially interfering with system installed components). If you have generated your own Python, you must ensure that it is consistently used (for all the cases you are concerned by). -- https://mail.python.org/mailman/listinfo/python-list
