diff options
| author | Simon Marchi <simon.marchi@polymtl.ca> | 2021-06-22 14:16:01 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2021-06-22 14:47:10 -0400 |
| commit | 4e317a765bbe1c47fb9d461b7effa40f34220c85 (patch) | |
| tree | 2b3b5d3b0e1461e238904472b72a6e8e6b99fc93 /gdb/ChangeLog | |
| parent | 80d1206d7fea6eb756183e2825abdfd0f00cd976 (diff) | |
| download | fsf-binutils-gdb-4e317a765bbe1c47fb9d461b7effa40f34220c85.zip fsf-binutils-gdb-4e317a765bbe1c47fb9d461b7effa40f34220c85.tar.gz fsf-binutils-gdb-4e317a765bbe1c47fb9d461b7effa40f34220c85.tar.bz2 | |
gdb/python: print name of unwinder that claimed frame in debug message
If we have multiple registered unwinders, this will helps identify which
unwinder was chosen and make it easier to track down potential problems.
Unwinders have a mandatory name argument, which we can use in the
message.
First, make gdb._execute_unwinders return a tuple containing the name,
in addition to the UnwindInfo. Then, make pyuw_sniffer include the name
in the debug message.
I moved the debug message earlier. I think it's good to print it as
early as possible, so that we see it in case an assert is hit in the
loop below, for example.
gdb/ChangeLog:
* python/lib/gdb/__init__.py (_execute_unwinders): Return tuple
with name of chosen unwinder.
* python/py-unwind.c (pyuw_sniffer): Print name of chosen
unwinder in debug message.
Change-Id: Id603545b44a97df2a39dd1872fe1f38ad5059f03
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index d9e0a3a..995c8a1 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,10 @@ +2021-06-22 Simon Marchi <simon.marchi@polymtl.ca> + + * python/lib/gdb/__init__.py (_execute_unwinders): Return tuple + with name of chosen unwinder. + * python/py-unwind.c (pyuw_sniffer): Print name of chosen + unwinder in debug message. + 2021-06-22 Andreas Schwab <schwab@suse.de> PR symtab/27999 |