Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #68201

Re: gdb unable to read python frame information

From dieter <dieter@handshake.de>
Subject Re: gdb unable to read python frame information
Date 2014-03-11 08:28 +0100
References (3 earlier) <00b321ae-2fb9-4360-93e4-e7f376444029@googlegroups.com> <mailman.7976.1394416133.18130.python-list@python.org> <ba897815-b155-4537-a51a-ea16b4b725c9@googlegroups.com> <mailman.7981.1394436528.18130.python-list@python.org> <09ebd498-fb4a-4036-8703-9f7c7a580ffa@googlegroups.com>
Newsgroups comp.lang.python
Message-ID <mailman.8036.1394522926.18130.python-list@python.org> (permalink)

Show all headers | View raw

Wesley <nispray@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).

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-06 18:03 -0800
  Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-07 08:10 +0100
    Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-07 02:29 -0800
      Re: gdb unable to read python frame information Ned Deily <nad@acm.org> - 2014-03-07 12:47 -0800
        Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-08 05:31 -0800
          Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-08 06:55 -0800
      Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-08 07:45 +0100
  Re: gdb unable to read python frame information Neal Becker <ndbecker2@gmail.com> - 2014-03-07 08:23 -0500
    Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-08 05:32 -0800
      Re: gdb unable to read python frame information Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-08 14:14 +0000
        Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-08 07:01 -0800
          Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-10 08:13 +0100
  Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-08 19:49 -0800
    Re: gdb unable to read python frame information Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-09 14:57 +0000
      Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-09 18:06 -0700
        Re: gdb unable to read python frame information Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-10 01:48 +0000
          Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-09 19:54 -0700
            Re: gdb unable to read python frame information Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-10 03:11 +0000
            Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-10 08:28 +0100
              Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-10 18:43 -0700
                Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-11 08:28 +0100
              Re: gdb unable to read python frame information Wesley <nispray@gmail.com> - 2014-03-10 20:01 -0700
                Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-11 08:31 +0100
        Re: gdb unable to read python frame information dieter <dieter@handshake.de> - 2014-03-10 08:16 +0100
    Re: gdb unable to read python frame information Terry Reedy <tjreedy@udel.edu> - 2014-03-09 14:37 -0400

csiph-web