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

Groups > comp.lang.python > #67975 > unrolled thread

gdb unable to read python frame information

Back to article view | Back to comp.lang.python

Contents

  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

Page 2 of 2 — ← Prev page 1 [2]

#68201

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).

[toc] | [prev] | [next] | [standalone]

#68193

Now, I fixed the problem...

Instead of python2.6.6, for python 2.7 it's OK..

Why? gdb does not support python 2.6.6?

Is it related to python-gdb.py? I googled a lot, seems only has python2.7-gdb.py, no python2.6-gdb.py.


在 2014年3月10日星期一UTC+8下午3时28分30秒，dieter写道：
> Wesley <nispray@gmail.com> writes:
> 
> 
> 
> > If you don't read the loop from the top, and don't tell me exactly what you want by just keep saying context, please ingore this post.
> 
> 
> 
> You are doing things only a few people do: trying to debug
> 
> a Python process on C level -- and you observe really strange things.
> 
> It is very difficult to guess from the distance what goes wrong.
> 
> 
> 
> Apparently, your gdb sees a very strange state of the debugged
> 
> process. But why?
> 
> 
> 
> Missing symbols was the first guess (the
> 
> gdb output you have provided does not suggest this - but
> 
> I have not seen the "reading symbols from "python" ..."; thus,
> 
> there may still be a problem with this).
> 
> 
> 
> A runaway process is another guess.
> 
> 
> 
> Some gdb problem another one.
> 
> 
> 
> 
> 
> I would approach the situation by simplifying the setup.
> 
> Instead of attaching a running Python process, I would
> 
> use "gdb python"; then "run"; then "CTRL-C" and there look
> 
> what "bt" gives you (this should demonstrate whether your
> 
> "gdb" is set up correctly and can debug Python on C level).
> 
> Then you write an infinitely running function in Python,
> 
> run it and again interrupt with "gdb" to see whether the "py-*"
> 
> commands are working. If this all work, you come again
> 
> to your actual task -- understanding what your python process
> 
> is doing.

[toc] | [prev] | [next] | [standalone]

#68202

Wesley <nispray@gmail.com> writes:

> Now, I fixed the problem...
>
> Instead of python2.6.6, for python 2.7 it's OK..
>
> Why? gdb does not support python 2.6.6?

gdb supports python 2.6.6 as well (it is a C level debugger with
very few dependencies on Python).

Your reports seem to suggest that your Python 2.6.6 installation
is somehow screwed up - for whatever reason.


> Is it related to python-gdb.py?

Very unlikely.

[toc] | [prev] | [next] | [standalone]

#68123

Mark Lawrence <breamoreboy@yahoo.co.uk> writes:
> On 10/03/2014 01:06, Wesley wrote:
> ...
> Context, you just keep sending messages like the above which on its
> own is meaningless.

The original poster has send messages lacking important pieces
of information -- but on request from the list, he has fixed this
initial error. Thus, on his side, there was progress ;-)

[toc] | [prev] | [next] | [standalone]

#68086

On 3/9/2014 10:57 AM, Mark Lawrence wrote:
> On 09/03/2014 03:49, Wesley wrote:
>> Anybody has suggestions?

Don't expect crazy things.
Send suggestions to the right place (a gdb list for a gdb enhancement).

>> This really makes me crazy...

> What makes you crazy?

The supposed fact that GnuDeBug does not understand Python frames on the 
stack.

 > You keep sending messages with no context.  We
> might be smart, but we're not (yet :) mind readers.

But we do speculate ;-)

-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python

csiph-web