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

Groups > comp.lang.python > #68124

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-10 08:28 +0100
References (1 earlier) <9c70d96c-3ab4-436c-aa90-82f47756ed6c@googlegroups.com> <mailman.7955.1394377206.18130.python-list@python.org> <00b321ae-2fb9-4360-93e4-e7f376444029@googlegroups.com> <mailman.7976.1394416133.18130.python-list@python.org> <ba897815-b155-4537-a51a-ea16b4b725c9@googlegroups.com>
Newsgroups comp.lang.python
Message-ID <mailman.7981.1394436528.18130.python-list@python.org> (permalink)

Show all headers | View raw

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.

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