This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail
- From: Tom Tromey <tromey at redhat dot com>
- To: Hui Zhu <hui_zhu at mentor dot com>
- Cc: gdb-patches ml <gdb-patches at sourceware dot org>
- Date: Tue, 14 Jan 2014 09:09:52 -0700
- Subject: Re: [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail
- Authentication-results: sourceware.org; auth=none
- References: <52974146 dot 70805 at mentor dot com> <8761r7w85h dot fsf at fleche dot redhat dot com> <529D8865 dot 80503 at mentor dot com> <87li01smua dot fsf at fleche dot redhat dot com> <529EDCA7 dot 1090903 at mentor dot com> <87eh5j2vw0 dot fsf at fleche dot redhat dot com> <52AAF43B dot 5060603 at mentor dot com>
>>>>> "Hui" == Hui Zhu <hui_zhu@mentor.com> writes:
Hui> With this patch, GDB will output a lot of "Python not initialized"
Hui> that output by function "ensure_python_env".
Hui> For example:
Hui> (gdb) start
Hui> Temporary breakpoint 1 at 0x400507: file 2.c, line 4.
Hui> Starting program: /home/teawater/tmp/2
Hui> Python not initialized
I think this may be an independent bug.
I'll have a better patch soon.
Tom