Message 263747 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	tilsche, vstinner
Date	2016-04-19.15:05:50
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1461078350.8.0.646153141318.issue26799@psf.upfronthosting.co.za>
In-reply-to

Content
I tried Python 3.6 with "./configure --with-pydebug --without-pymalloc --with-valgrind". The py-bt commands works as expect in gdb. Can you try to modify python-gdb.py to get a traceback of your Invalid cast error? > I am able to fix it with the following commands: > (...) _type_char_ptr = gdb.lookup_type('char').pointer() # char* These defines are already in Tools/gdb/libpython.py (python-gdb.py is just a copy). I don't understand why you have to redeclare these variables again.

I tried Python 3.6 with "./configure --with-pydebug --without-pymalloc --with-valgrind". The py-bt commands works as expect in gdb.

Can you try to modify python-gdb.py to get a traceback of your Invalid cast error?

> I am able to fix it with the following commands:
> (...) _type_char_ptr = gdb.lookup_type('char').pointer() # char*

These defines are already in Tools/gdb/libpython.py (python-gdb.py is just a copy). I don't understand why you have to redeclare these variables again.

History
Date	User	Action	Args
2016-04-19 15:05:50	vstinner	set	recipients: + vstinner, tilsche
2016-04-19 15:05:50	vstinner	set	messageid: <1461078350.8.0.646153141318.issue26799@psf.upfronthosting.co.za>
2016-04-19 15:05:50	vstinner	link	issue26799 messages
2016-04-19 15:05:50	vstinner	create