* ping [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail
@ 2014-06-16 15:27 Programmingkid
0 siblings, 0 replies; only message in thread
From: Programmingkid @ 2014-06-16 15:27 UTC (permalink / raw)
To: gdb
I am pinging this patch to be considered for the next release of gdb. It fixes the error message that is displayed with a backtrace.
It is originally found here: http://www.sourceware.org/ml/gdb-patches/2013-11/msg00881.html
2013-11-28 Hui Zhu <hui@codesourcery.com>
* python/py-framefilter.c(apply_frame_filter): Add check for
"gdb_python_module".
--- a/gdb/python/py-framefilter.c
+++ b/gdb/python/py-framefilter.c
@@ -1506,7 +1506,10 @@ apply_frame_filter (struct frame_info *f
initialization error. This return code will trigger a
default backtrace. */
- gdbpy_print_stack ();
+ if (gdb_python_module != NULL)
+ gdbpy_print_stack ();
+ else
+ PyErr_Clear ();
do_cleanups (cleanups);
return PY_BT_NO_FILTERS;
}
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-06-16 15:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-16 15:27 ping [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail Programmingkid
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).