c7081b119c
* reverse debugging on aarch64
* new commands or subcommands:
- info os cpu, set/show serial parity, info dll
- maint print symbol-cache/symbol-cache-statistics,
maint flush-symbol-cache
- record btrace bts, record bts
- compile print
- show/set mpx bound
- tui enable/disable
- record btrace pt, record pt
- maint info btrace,
maint btrace packet-history/clear-packet-history/clear
* s390 support for vector ABI
* "set sysroot" improvements related to remote targets
* better support for debugging containerized programs
(without "set sysroot")
* HISTSIZE environment variable is replaced by GDBHISTSIZE
* python scripting:
- it's possible to write frame unwinders
- several new methods in Objfile, Type and Value classes
- gdb can auto-load scripts contained in special sections
named '.debug_gdb_scripts'.
* extensions for the MI interface, new remote packet types
- Removed obsolete patches:
0001-S390-Add-target-descriptions-for-vector-register-set.patch
0001-S390-Fix-compiler-invocation-with-compile-command.patch
0001-S390-Support-new-vector-register-sections.patch
0002-S390-Add-vector-register-support-to-gdb.patch
0003-S390-Add-vector-register-support-to-gdbserver.patch
OBS-URL: https://build.opensuse.org/package/show/devel:gcc/gdb?expand=0&rev=128
86 lines
3.1 KiB
Diff
86 lines
3.1 KiB
Diff
This should fix the error with glib. An error message will still be
|
|
printed, but a default backtrace will occur in this case.
|
|
|
|
--
|
|
|
|
Index: gdb-7.9.50.20150520/gdb/python/py-framefilter.c
|
|
===================================================================
|
|
--- gdb-7.9.50.20150520.orig/gdb/python/py-framefilter.c 2015-05-31 17:36:34.681952530 +0200
|
|
+++ gdb-7.9.50.20150520/gdb/python/py-framefilter.c 2015-05-31 17:55:01.884788031 +0200
|
|
@@ -1523,6 +1523,7 @@ gdbpy_apply_frame_filter (const struct e
|
|
PyObject *iterable;
|
|
PyObject *item;
|
|
htab_t levels_printed;
|
|
+ int count_printed = 0;
|
|
|
|
if (!gdb_python_initialized)
|
|
return EXT_LANG_BT_NO_FILTERS;
|
|
@@ -1543,24 +1544,7 @@ gdbpy_apply_frame_filter (const struct e
|
|
iterable = bootstrap_python_frame_filters (frame, frame_low, frame_high);
|
|
|
|
if (iterable == NULL)
|
|
- {
|
|
- /* Normally if there is an error GDB prints the exception,
|
|
- abandons the backtrace and exits. The user can then call "bt
|
|
- no-filters", and get a default backtrace (it would be
|
|
- confusing to automatically start a standard backtrace halfway
|
|
- through a Python filtered backtrace). However in the case
|
|
- where GDB cannot initialize the frame filters (most likely
|
|
- due to incorrect auto-load paths), GDB has printed nothing.
|
|
- In this case it is OK to print the default backtrace after
|
|
- printing the error message. GDB returns EXT_LANG_BT_NO_FILTERS
|
|
- here to signify there are no filters after printing the
|
|
- initialization error. This return code will trigger a
|
|
- default backtrace. */
|
|
-
|
|
- gdbpy_print_stack ();
|
|
- do_cleanups (cleanups);
|
|
- return EXT_LANG_BT_NO_FILTERS;
|
|
- }
|
|
+ goto error_nothing_printed;
|
|
|
|
/* If iterable is None, then there are no frame filters registered.
|
|
If this is the case, defer to default GDB printing routines in MI
|
|
@@ -1591,15 +1575,40 @@ gdbpy_apply_frame_filter (const struct e
|
|
error and continue with other frames. */
|
|
if (success == EXT_LANG_BT_ERROR)
|
|
gdbpy_print_stack ();
|
|
+
|
|
+ count_printed++;
|
|
}
|
|
|
|
if (item == NULL && PyErr_Occurred ())
|
|
- goto error;
|
|
+ {
|
|
+ if (count_printed > 0)
|
|
+ goto error;
|
|
+ else
|
|
+ goto error_nothing_printed;
|
|
+ }
|
|
|
|
done:
|
|
do_cleanups (cleanups);
|
|
return success;
|
|
|
|
+ /* Normally if there is an error GDB prints the exception,
|
|
+ abandons the backtrace and exits. The user can then call "bt
|
|
+ no-filters", and get a default backtrace (it would be
|
|
+ confusing to automatically start a standard backtrace halfway
|
|
+ through a Python filtered backtrace). However in the case
|
|
+ where GDB cannot initialize the frame filters (most likely
|
|
+ due to incorrect auto-load paths), GDB has printed nothing.
|
|
+ In this case it is OK to print the default backtrace after
|
|
+ printing the error message. GDB returns EXT_LANG_BT_NO_FILTERS
|
|
+ here to signify there are no filters after printing the
|
|
+ initialization error. This return code will trigger a
|
|
+ default backtrace. */
|
|
+
|
|
+ error_nothing_printed:
|
|
+ gdbpy_print_stack ();
|
|
+ do_cleanups (cleanups);
|
|
+ return EXT_LANG_BT_NO_FILTERS;
|
|
+
|
|
/* Exit and abandon backtrace on error, printing the exception that
|
|
is set. */
|
|
error:
|