Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Albert Chin <gdb@mlists.thewrittenword.com>
To: gdb@sourceware.org
Subject: Building GDB 7.10 with Python support
Date: Fri, 09 Oct 2015 21:56:00 -0000	[thread overview]
Message-ID: <20151009215602.GA15880@thewrittenword.com> (raw)

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)


             reply	other threads:[~2015-10-09 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 21:56 Albert Chin [this message]
2015-10-10  7:09 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151009215602.GA15880@thewrittenword.com \
    --to=gdb@mlists.thewrittenword.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox