Building GDB 7.10 with Python support

Albert Chin
2015-10-09T21:56:09Z

I built a custom version of Python 2.7.5 for RHEL 6/x86-64 and am
trying to use it to build gdb-7.10. I can build gdb-7.10 but it has
problems:
$ gtar Jxf gdb-7.10.tar.xz
$ cd gdb-7.10
$ PATH=/opt/TWWfsw/python27/bin:$PATH \
CFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config" \
LDFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config \
-Wl,-rpath,/opt/TWWfsw/python27/lib/python2.7/config" \
./configure --prefix=/tmp/gdb
$ PATH=/opt/TWWfsw/python27/bin:$PATH \
CFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config" \
LDFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config \
-Wl,-rpath,/opt/TWWfsw/python27/lib/python2.7/config" \
make
$ PATH=/opt/TWWfsw/python27/bin:$PATH \
CFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config" \
LDFLAGS="-I/opt/TWWfsw/python27/lib/python2.7/config \
-Wl,-rpath,/opt/TWWfsw/python27/lib/python2.7/config" \
make install

$ ldd /tmp/gdb/bin/gdb
linux-vdso.so.1 => (0x00007fffa7fe4000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000030e3000000)
libncurses.so.5 => /lib64/libncurses.so.5 (0x0000003fb2200000)
libm.so.6 => /lib64/libm.so.6 (0x00000030e2c00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000030e3400000)
libutil.so.1 => /lib64/libutil.so.1 (0x00000030f2800000)
libpython2.7.so => /opt/TWWfsw/python27/lib/python2.7/config/libpython2.7.so (0x00007feaec72d000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x000000359b800000)
libc.so.6 => /lib64/libc.so.6 (0x00000030e2800000)
libtinfo.so.5 => /lib64/libtinfo.so.5 (0x0000003fb1200000)
/lib64/ld-linux-x86-64.so.2 (0x00000030e2000000)

$ /tmp/gdb/bin/gdb a.out
...
(gdb) break main
Breakpoint 1 at 0x4004c8: file d.c, line 57.
(gdb) r
Starting program: /opt/src/latest/devel/gdb-7.10/a.out
A Unwinder should return gdb.UnwindInfo instance.
findvar.c:290: internal-error: value_of_register_lazy: Assertion `frame_id_p (get_frame_id (frame))' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

Any ideas where I can start looking? The Python 2.7.5 I built seems to
work ok outside of this issue.

--
albert chin (china@thewrittenword.com)