This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC][patch 1/9] initial Python support
- From: Tom Tromey <tromey at redhat dot com>
- To: thiagoju at linux dot ibm dot com
- Cc: Daniel Jacobowitz <drow at false dot org>, Thiago Jung Bauermann <bauerman at br dot ibm dot com>, gdb-patches at sourceware dot org
- Date: Sun, 06 Jul 2008 11:27:33 -0600
- Subject: Re: [RFC][patch 1/9] initial Python support
- References: <20080429155212.444237503@br.ibm.com> <20080429155304.288626880@br.ibm.com> <20080528205921.GA2969@caradoc.them.org> <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> <m3lk0wysfp.fsf@fleche.redhat.com>
- Reply-to: tromey at redhat dot com
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>>> > + if (PyErr_Occurred ())
>>> > + {
>>> > + PyErr_Print ();
>>> > + error ("error while executing Python code");
>>> > + }
>>> > +}
Thiago> This is stillpending, I think.
FYI -- I fixed this today. I added a new 'maint set python-stack'
variable that controls whether Python stack traces are printed. By
default they are. I changed all the new code to use a new
gdbpy_print_stack which checks this variable. Finally, I set things
up so that gdb overrides Python's sys.stdout and sys.stderr to print
things using printf_filtered.
Tom