public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vovcat at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/18393] GDB 7.9 segfaults on: python dir(gdb.current_progspace())
Date: Sun, 27 Sep 2015 22:51:00 -0000 [thread overview]
Message-ID: <bug-18393-4717-h9BZpsiJNh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18393-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18393
vovcat at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vovcat at gmail dot com
Component|gdb |python
Version|7.9 |7.10
--- Comment #2 from vovcat at gmail dot com ---
$ gdb -ex 'python dir(gdb.objfiles()[0])' /bin/ls
GNU gdb (Debian 7.10-1) 7.10
[...]
Reading symbols from /bin/ls...(no debugging symbols found)...done.
Segmentation fault (core dumped)
$ gdb /usr/bin/gdb /var/tmp/1001.gdb.11.10618
[...]
Reading symbols from /usr/bin/gdb...Reading symbols from
/usr/lib/debug/.build-id/c6/f43bbad2fe64d3ce948335d7ccf97cee9f8d93.debug...done.
done.
[New LWP 10618]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `gdb -ex python dir(gdb.objfiles()[0]) /bin/ls'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 gdb_py_generic_dict (self=0xb6b5bfc0,
closure=0x861df60 <objfile_object_type>)
at /build/gdb-ywwWgT/gdb-7.10/gdb/python/py-utils.c:429
429 /build/gdb-ywwWgT/gdb-7.10/gdb/python/py-utils.c: No such file or
directory.
(gdb) bt
#0 gdb_py_generic_dict (self=0xb6b5bfc0,
closure=0x861df60 <objfile_object_type>)
at /build/gdb-ywwWgT/gdb-7.10/gdb/python/py-utils.c:429
#1 0xb7452bab in ?? () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#2 0xb72b13e9 in _PyObject_GenericGetAttrWithDict ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#3 0xb72b162e in PyObject_GenericGetAttr ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#4 0xb72a3a20 in PyObject_GetAttr ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#5 0xb72a3bcc in _PyObject_GetAttrId ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#6 0xb72bf153 in ?? () from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#7 0xb72c767f in PyCFunction_Call ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#8 0xb73d20e3 in PyObject_Call ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#9 0xb741c79d in PyObject_CallFunctionObjArgs ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
#10 0xb72b0f85 in PyObject_Dir ()
from /usr/lib/i386-linux-gnu/libpython3.4m.so.1.0
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-27 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 21:33 [Bug gdb/18393] New: " zachriggle+gdb at gmail dot com
2015-05-09 21:43 ` [Bug gdb/18393] " zachriggle+gdb at gmail dot com
2015-09-27 22:51 ` vovcat at gmail dot com [this message]
2015-09-27 22:55 ` [Bug python/18393] " vovcat at gmail dot com
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=bug-18393-4717-h9BZpsiJNh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).