2023-03-31 16:53:54 +00:00
|
|
|
# Check distro name is included in the version output.
|
2017-12-08 04:31:26 +00:00
|
|
|
Patch001: gdb-6.3-rh-testversion-20041202.patch
|
|
|
|
|
|
|
|
|
|
# Add a wrapper script to GDB that implements pstack using the
|
|
|
|
|
# --readnever option.
|
|
|
|
|
#=push
|
2021-06-06 21:54:47 +00:00
|
|
|
Patch002: gdb-6.3-gstack-20050411.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Test sideeffects of skipping ppc .so libs trampolines (BZ 218379).
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch003: gdb-6.5-bz218379-ppc-solib-trampoline-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Allow running `/usr/bin/gcore' with provided but inaccessible tty (BZ 229517).
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch004: gdb-6.6-bz229517-gcore-without-terminal.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Avoid too long timeouts on failing cases of "annota1.exp annota3.exp".
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch005: gdb-6.6-testsuite-timeouts.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Support for stepping over PPC atomic instruction sequences (BZ 237572).
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch006: gdb-6.6-bz237572-ppc-atomic-sequence-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Test leftover zombie process (BZ 243845).
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch007: gdb-6.5-bz243845-stale-testing-zombie-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# New locating of the matching binaries from the pure core file (build-id).
|
|
|
|
|
#=push+jan
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch008: gdb-6.6-buildid-locate.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix loading of core files without build-ids but with build-ids in executables.
|
|
|
|
|
# Load strictly build-id-checked core files only if no executable is specified
|
|
|
|
|
# (Jan Kratochvil, RH BZ 1339862).
|
|
|
|
|
#=push+jan
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch009: gdb-6.6-buildid-locate-solib-missing-ids.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Test PPC hiding of call-volatile parameter register.
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch010: gdb-6.7-ppc-clobbered-registers-O2-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
2021-02-18 01:28:52 +00:00
|
|
|
# Test gcore memory and time requirements for large inferiors.
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch011: gdb-6.5-gcore-buffer-limit-test.patch
|
2021-02-18 01:28:52 +00:00
|
|
|
|
2017-12-08 04:31:26 +00:00
|
|
|
# Test GCORE for shmid 0 shared memory mappings.
|
|
|
|
|
#=fedoratest: But it is broken anyway, sometimes the case being tested is not reproducible.
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch012: gdb-6.3-mapping-zero-inode-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Test a crash on libraries missing the .text section.
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch013: gdb-6.5-section-num-fixup-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix resolving of variables at locations lists in prelinked libs (BZ 466901).
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch014: gdb-6.8-bz466901-backtrace-full-prelinked.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# New test for step-resume breakpoint placed in multiple threads at once.
|
|
|
|
|
#=fedoratest
|
2024-03-28 23:28:35 +00:00
|
|
|
Patch015: gdb-simultaneous-step-resume-breakpoint-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix follow-exec for C++ programs (bugreported by Martin Stransky).
|
|
|
|
|
#=fedoratest
|
Remove gdb-core-open-vdso-warning.patch
The tests added by this patch are similar to those of upstream test
gdb.base/vdso-warning.exp. I think that the upstream patch provides
better coverage in that it also provides tests involving core files.
This patch started out as a change to gdb in Jan 2010 changing
gdb/solib-svr4.c. There were no tests included in this initial
commit.
Tests were added in a commit from June 19, 2012, changing files
gdb.base/solib-symbol.exp and gdb.base/corefile.exp. There were also
changes made to gdb/solib.c.
Tweaks to the test cases were made in commits from July 3, 2012,
July 6, 2012, and Jan 19, 2013.
Many, maybe all, of the solib-svr4.c and solib.c changes were
removed in a commit from Feb 7, 2014. The gdb.base/corefile.exp
changes were removed at the same time. There is no explanation
in the log for why this was done. However, after reading some
gdb-patches discussion from that period, it appears that Jan
believed that the correct fix was in glibc and that having a
workaround in gdb weakened the argument for what he believed
to be a proper fix in glibc. Roland McGrath and Ulrich Drepper
disagreed with Jan regarding his proposed glibc change (from 2009).
An upstream ChangeLog entry from Oct 2014 shows that Jan and Pedro
added upstream test gdb.base/vdso-warning.exp. Also, at that time,
new code was added to GDB for handling the vdso problem. See
upstream PR 14466:
https://sourceware.org/bugzilla/show_bug.cgi?id=14466)
All further/subsequent changes to the local patch
gdb-core-open-vdso-warning.patch are rebase related.
Bottom line is that the remaining tests in gdb.base/solib-symbol.exp
are covered by an existing upstream test. The upstream test also
handles the core file case which had also once been handled by this
local test.
2024-06-15 02:28:34 +00:00
|
|
|
Patch016: gdb-archer-next-over-throw-cxx-exec.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# [delayed-symfile] Test a backtrace regression on CFIs without DIE (BZ 614604).
|
|
|
|
|
#=fedoratest
|
Remove gdb-core-open-vdso-warning.patch
The tests added by this patch are similar to those of upstream test
gdb.base/vdso-warning.exp. I think that the upstream patch provides
better coverage in that it also provides tests involving core files.
This patch started out as a change to gdb in Jan 2010 changing
gdb/solib-svr4.c. There were no tests included in this initial
commit.
Tests were added in a commit from June 19, 2012, changing files
gdb.base/solib-symbol.exp and gdb.base/corefile.exp. There were also
changes made to gdb/solib.c.
Tweaks to the test cases were made in commits from July 3, 2012,
July 6, 2012, and Jan 19, 2013.
Many, maybe all, of the solib-svr4.c and solib.c changes were
removed in a commit from Feb 7, 2014. The gdb.base/corefile.exp
changes were removed at the same time. There is no explanation
in the log for why this was done. However, after reading some
gdb-patches discussion from that period, it appears that Jan
believed that the correct fix was in glibc and that having a
workaround in gdb weakened the argument for what he believed
to be a proper fix in glibc. Roland McGrath and Ulrich Drepper
disagreed with Jan regarding his proposed glibc change (from 2009).
An upstream ChangeLog entry from Oct 2014 shows that Jan and Pedro
added upstream test gdb.base/vdso-warning.exp. Also, at that time,
new code was added to GDB for handling the vdso problem. See
upstream PR 14466:
https://sourceware.org/bugzilla/show_bug.cgi?id=14466)
All further/subsequent changes to the local patch
gdb-core-open-vdso-warning.patch are rebase related.
Bottom line is that the remaining tests in gdb.base/solib-symbol.exp
are covered by an existing upstream test. The upstream test also
handles the core file case which had also once been handled by this
local test.
2024-06-15 02:28:34 +00:00
|
|
|
Patch017: gdb-test-bt-cfi-without-die.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# [archer-tromey-delayed-symfile] New test gdb.dwarf2/dw2-aranges.exp.
|
|
|
|
|
#=fedoratest
|
Remove gdb-core-open-vdso-warning.patch
The tests added by this patch are similar to those of upstream test
gdb.base/vdso-warning.exp. I think that the upstream patch provides
better coverage in that it also provides tests involving core files.
This patch started out as a change to gdb in Jan 2010 changing
gdb/solib-svr4.c. There were no tests included in this initial
commit.
Tests were added in a commit from June 19, 2012, changing files
gdb.base/solib-symbol.exp and gdb.base/corefile.exp. There were also
changes made to gdb/solib.c.
Tweaks to the test cases were made in commits from July 3, 2012,
July 6, 2012, and Jan 19, 2013.
Many, maybe all, of the solib-svr4.c and solib.c changes were
removed in a commit from Feb 7, 2014. The gdb.base/corefile.exp
changes were removed at the same time. There is no explanation
in the log for why this was done. However, after reading some
gdb-patches discussion from that period, it appears that Jan
believed that the correct fix was in glibc and that having a
workaround in gdb weakened the argument for what he believed
to be a proper fix in glibc. Roland McGrath and Ulrich Drepper
disagreed with Jan regarding his proposed glibc change (from 2009).
An upstream ChangeLog entry from Oct 2014 shows that Jan and Pedro
added upstream test gdb.base/vdso-warning.exp. Also, at that time,
new code was added to GDB for handling the vdso problem. See
upstream PR 14466:
https://sourceware.org/bugzilla/show_bug.cgi?id=14466)
All further/subsequent changes to the local patch
gdb-core-open-vdso-warning.patch are rebase related.
Bottom line is that the remaining tests in gdb.base/solib-symbol.exp
are covered by an existing upstream test. The upstream test also
handles the core file case which had also once been handled by this
local test.
2024-06-15 02:28:34 +00:00
|
|
|
Patch018: gdb-test-dw2-aranges.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Testcase for `Setting solib-absolute-prefix breaks vDSO' (BZ 818343).
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch019: gdb-rhbz-818343-set-solib-absolute-prefix-testcase.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Import regression test for `gdb/findvar.c:417: internal-error:
|
|
|
|
|
# read_var_value: Assertion `frame' failed.' (RH BZ 947564) from RHEL 6.5.
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch020: gdb-rhbz947564-findvar-assertion-frame-failed-testcase.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix 'memory leak in infpy_read_memory()' (RH BZ 1007614)
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch021: gdb-rhbz1007614-memleak-infpy_read_memory-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix 'gdb gives highly misleading error when debuginfo pkg is present,
|
|
|
|
|
# but not corresponding binary pkg' (RH BZ 981154).
|
|
|
|
|
#=push+jan
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch022: gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Testcase for '[SAP] Recursive dlopen causes SAP HANA installer to
|
|
|
|
|
# crash.' (RH BZ 1156192).
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch023: gdb-rhbz1156192-recursive-dlopen-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix '`catch syscall' doesn't work for parent after `fork' is called'
|
|
|
|
|
# (Philippe Waroquiers, RH BZ 1149205).
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch024: gdb-rhbz1149205-catch-syscall-after-fork-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# Fix '[ppc64] and [s390x] wrong prologue skip on -O2 -g code' (Jan
|
|
|
|
|
# Kratochvil, RH BZ 1084404).
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch025: gdb-rhbz1084404-ppc64-s390x-wrong-prologue-skip-O2-g-3of3.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
|
|
|
|
# [aarch64] Fix hardware watchpoints (RH BZ 1261564).
|
|
|
|
|
#=fedoratest
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch026: gdb-rhbz1261564-aarch64-hw-watchpoint-test.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
Rewrite (and rename) gdb-libexec-add-index.patch
It has been observed that the changes added by
gdb-libexec-add-index.patch will result in GDB testing hanging when
the tests are being run using an in-tree GDB; that is when using 'make
check'. One test that is known to fail is gdb.base/with-mf.exp,
though any test that calls the gdb-add-index.sh script will also hang.
The problem is that when the gdb-add-index.sh script is run, the GDB
testsuite passes the GDB command to use within the GDB environment
variable. For in-tree testing this will be something like:
GDB="/path/to/gdb -data-directory /path/to/data-directory"
Notice that the environment variable contains both an executable and
an argument.
Our changes to gdb-add-index.sh add this:
GDB2=/usr/libexec/gdb
if test -x $GDB2 && ! which $GDB &>/dev/null; then
GDB=$GDB2
fi
The problem then is that '-data-directory' is treated as a set of
options to 'which'. Many of these options are not known to 'which',
but the '-i' option is known. The documentation of '-i' says:
--read-alias, -i
Read aliases from stdin, reporting matching ones on
stdout. This is useful in combination with using an alias for
which itself. For example
alias which=´alias | which -i´.
And here's the problem; this option causes 'which' to read from
stdin. As the GDB testsuite doesn't send any additional input on
stdin then the which command will never complete, and the test will
hang.
The solution I think is to avoid calling 'which' like this on a user
supplied GDB environment variable.
The changes in the gdb-libexec-add-index.patch were really about what
the _default_ GDB executable should be. The upstream version of this
script does this:
GDB=${GDB:=gdb}
That is, the default is just 'gdb'. However, for RH this is not good
enough. We want to handle two additional cases, first, when only the
gdb-minimal package is installed, in which case the default should be
/usr/bin/gdb.minimal. Then we also want to handle the case where the
user doesn't have 'gdb' itself in their $PATH, but does have the 'gdb'
executable installed in /usr/libexec/gdb.
The code as it currently stands also has a problem where, if
gdb.minimal is installed on the machine this will _always_ be used in
preference to the user supplied GDB value (assuming the code worked at
all) this means that when doing in-tree testing we wouldn't actually
be using the in-tree GDB to build the index, which isn't ideal.
So in this commit I propose that we rework our gdb-add-index.sh
changes. Now, we only use the RH special values in the case that
there is no GDB environment variable set. I believe this handles all
the required use cases:
1. When doing in-tree testing GDB environment variable will be set,
and this will always be used as is, with no special processing,
2. When gdb-add-index.sh is used and GDB environment variable is not
set then we will use the first of the following as the default:
(a) /usr/bin/gdb.minimal if this file exists and is executable,
(b) The first gdb executable that can be found in the $PATH,
(c) /usr/libexec/gdb if this file exists and is executable.
While I was changing this patch anyway I've removed the libexec part
of the patch name -- this no longer seemed relevant, I suspect this
related to an older version of this patch.
2023-05-04 13:48:16 +00:00
|
|
|
# Update gdb-add-index.sh such that, when the GDB environment
|
|
|
|
|
# variable is not set, the script is smarter than just looking for
|
|
|
|
|
# 'gdb' in the $PATH.
|
2019-04-29 00:46:29 +00:00
|
|
|
#
|
Rewrite (and rename) gdb-libexec-add-index.patch
It has been observed that the changes added by
gdb-libexec-add-index.patch will result in GDB testing hanging when
the tests are being run using an in-tree GDB; that is when using 'make
check'. One test that is known to fail is gdb.base/with-mf.exp,
though any test that calls the gdb-add-index.sh script will also hang.
The problem is that when the gdb-add-index.sh script is run, the GDB
testsuite passes the GDB command to use within the GDB environment
variable. For in-tree testing this will be something like:
GDB="/path/to/gdb -data-directory /path/to/data-directory"
Notice that the environment variable contains both an executable and
an argument.
Our changes to gdb-add-index.sh add this:
GDB2=/usr/libexec/gdb
if test -x $GDB2 && ! which $GDB &>/dev/null; then
GDB=$GDB2
fi
The problem then is that '-data-directory' is treated as a set of
options to 'which'. Many of these options are not known to 'which',
but the '-i' option is known. The documentation of '-i' says:
--read-alias, -i
Read aliases from stdin, reporting matching ones on
stdout. This is useful in combination with using an alias for
which itself. For example
alias which=´alias | which -i´.
And here's the problem; this option causes 'which' to read from
stdin. As the GDB testsuite doesn't send any additional input on
stdin then the which command will never complete, and the test will
hang.
The solution I think is to avoid calling 'which' like this on a user
supplied GDB environment variable.
The changes in the gdb-libexec-add-index.patch were really about what
the _default_ GDB executable should be. The upstream version of this
script does this:
GDB=${GDB:=gdb}
That is, the default is just 'gdb'. However, for RH this is not good
enough. We want to handle two additional cases, first, when only the
gdb-minimal package is installed, in which case the default should be
/usr/bin/gdb.minimal. Then we also want to handle the case where the
user doesn't have 'gdb' itself in their $PATH, but does have the 'gdb'
executable installed in /usr/libexec/gdb.
The code as it currently stands also has a problem where, if
gdb.minimal is installed on the machine this will _always_ be used in
preference to the user supplied GDB value (assuming the code worked at
all) this means that when doing in-tree testing we wouldn't actually
be using the in-tree GDB to build the index, which isn't ideal.
So in this commit I propose that we rework our gdb-add-index.sh
changes. Now, we only use the RH special values in the case that
there is no GDB environment variable set. I believe this handles all
the required use cases:
1. When doing in-tree testing GDB environment variable will be set,
and this will always be used as is, with no special processing,
2. When gdb-add-index.sh is used and GDB environment variable is not
set then we will use the first of the following as the default:
(a) /usr/bin/gdb.minimal if this file exists and is executable,
(b) The first gdb executable that can be found in the $PATH,
(c) /usr/libexec/gdb if this file exists and is executable.
While I was changing this patch anyway I've removed the libexec part
of the patch name -- this no longer seemed relevant, I suspect this
related to an older version of this patch.
2023-05-04 13:48:16 +00:00
|
|
|
# The actual search order is now: /usr/bin/gdb.minimal, gdb (in the
|
|
|
|
|
# $PATH), then /usr/libexec/gdb.
|
|
|
|
|
#
|
|
|
|
|
# For the rationale of looking for gdb.minimal see:
|
2019-04-29 00:46:29 +00:00
|
|
|
#
|
|
|
|
|
# https://fedoraproject.org/wiki/Changes/Minimal_GDB_in_buildroot
|
Rewrite (and rename) gdb-libexec-add-index.patch
It has been observed that the changes added by
gdb-libexec-add-index.patch will result in GDB testing hanging when
the tests are being run using an in-tree GDB; that is when using 'make
check'. One test that is known to fail is gdb.base/with-mf.exp,
though any test that calls the gdb-add-index.sh script will also hang.
The problem is that when the gdb-add-index.sh script is run, the GDB
testsuite passes the GDB command to use within the GDB environment
variable. For in-tree testing this will be something like:
GDB="/path/to/gdb -data-directory /path/to/data-directory"
Notice that the environment variable contains both an executable and
an argument.
Our changes to gdb-add-index.sh add this:
GDB2=/usr/libexec/gdb
if test -x $GDB2 && ! which $GDB &>/dev/null; then
GDB=$GDB2
fi
The problem then is that '-data-directory' is treated as a set of
options to 'which'. Many of these options are not known to 'which',
but the '-i' option is known. The documentation of '-i' says:
--read-alias, -i
Read aliases from stdin, reporting matching ones on
stdout. This is useful in combination with using an alias for
which itself. For example
alias which=´alias | which -i´.
And here's the problem; this option causes 'which' to read from
stdin. As the GDB testsuite doesn't send any additional input on
stdin then the which command will never complete, and the test will
hang.
The solution I think is to avoid calling 'which' like this on a user
supplied GDB environment variable.
The changes in the gdb-libexec-add-index.patch were really about what
the _default_ GDB executable should be. The upstream version of this
script does this:
GDB=${GDB:=gdb}
That is, the default is just 'gdb'. However, for RH this is not good
enough. We want to handle two additional cases, first, when only the
gdb-minimal package is installed, in which case the default should be
/usr/bin/gdb.minimal. Then we also want to handle the case where the
user doesn't have 'gdb' itself in their $PATH, but does have the 'gdb'
executable installed in /usr/libexec/gdb.
The code as it currently stands also has a problem where, if
gdb.minimal is installed on the machine this will _always_ be used in
preference to the user supplied GDB value (assuming the code worked at
all) this means that when doing in-tree testing we wouldn't actually
be using the in-tree GDB to build the index, which isn't ideal.
So in this commit I propose that we rework our gdb-add-index.sh
changes. Now, we only use the RH special values in the case that
there is no GDB environment variable set. I believe this handles all
the required use cases:
1. When doing in-tree testing GDB environment variable will be set,
and this will always be used as is, with no special processing,
2. When gdb-add-index.sh is used and GDB environment variable is not
set then we will use the first of the following as the default:
(a) /usr/bin/gdb.minimal if this file exists and is executable,
(b) The first gdb executable that can be found in the $PATH,
(c) /usr/libexec/gdb if this file exists and is executable.
While I was changing this patch anyway I've removed the libexec part
of the patch name -- this no longer seemed relevant, I suspect this
related to an older version of this patch.
2023-05-04 13:48:16 +00:00
|
|
|
#
|
2017-12-08 04:31:26 +00:00
|
|
|
#=fedora
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch027: gdb-add-index.patch
|
2017-12-08 04:31:26 +00:00
|
|
|
|
2023-11-28 15:20:27 +00:00
|
|
|
# Back-port upstream commit 1f0fab7ff86 as part of a fix for
|
|
|
|
|
# non-deterministic gdb-index generation (RH BZ 2232086).
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch028: gdb-rhbz2232086-refactor-selftest-support.patch
|
2023-11-28 15:20:27 +00:00
|
|
|
|
|
|
|
|
# Back-port upstream commit aa19bc1d259 as part of a fix for
|
|
|
|
|
# non-deterministic gdb-index generation (RH BZ 2232086).
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch029: gdb-rhbz-2232086-reduce-size-of-gdb-index.patch
|
2023-11-28 15:20:27 +00:00
|
|
|
|
|
|
|
|
# Back-port upstream commit acc117b57f7 as part of a fix for
|
|
|
|
|
# non-deterministic gdb-index generation (RH BZ 2232086).
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch030: gdb-rhbz-2232086-cpp-ify-mapped-symtab.patch
|
2023-11-28 15:20:27 +00:00
|
|
|
|
|
|
|
|
# Back-port upstream commit aff250145af as part of a fix for
|
|
|
|
|
# non-deterministic gdb-index generation (RH BZ 2232086).
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch031: gdb-rhbz-2232086-generate-gdb-index-consistently.patch
|
2023-11-28 15:20:27 +00:00
|
|
|
|
|
|
|
|
# Back-port upstream commit 3644f41dc80 as part of a fix for
|
|
|
|
|
# non-deterministic gdb-index generation (RH BZ 2232086).
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch032: gdb-rhbz-2232086-generate-dwarf-5-index-consistently.patch
|
2023-11-28 15:20:27 +00:00
|
|
|
|
2024-01-08 12:32:04 +00:00
|
|
|
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch033: gdb-rhbz2250652-gdbpy_gil.patch
|
2024-01-08 12:32:04 +00:00
|
|
|
|
|
|
|
|
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch034: gdb-rhbz2250652-avoid-PyOS_ReadlineTState.patch
|
2024-01-08 12:32:04 +00:00
|
|
|
|
2024-01-17 03:12:34 +00:00
|
|
|
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch035: gdb-ftbs-swapped-calloc-args.patch
|
2024-01-24 10:17:46 +00:00
|
|
|
|
2024-01-29 22:55:13 +00:00
|
|
|
# Backport upstream workaround for GCC 14 problem which cause assertion
|
|
|
|
|
# failures in GDB.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch036: gdb-rhbz2261580-intrusive_list-assertion-fix.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 7628a997f27.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch037: gdb-sync-coffread-with-elfread.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 27807da5849.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch038: gdb-merge-debug-symbol-lookup.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 6234ba17598.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch039: gdb-refactor-find-and-add-separate-symbol-file.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 661d98a3331.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch040: gdb-add-missing-debug-ext-lang-hook.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 8f6c452b5a4.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch041: gdb-add-missing-debug-info-python-hook.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 7db795bc67a.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch042: gdb-remove-use-of-py-isascii
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 1146d27749f.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch043: gdb-remove-path-in-test-name.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit e8c3dafa5f5.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch044: gdb-do-not-import-py-curses-ascii-module.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit dd5516bf98f.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch045: gdb-reformat-missing-debug-py-file.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Backport upstream commit 7d21600b31fe.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch046: gdb-handle-no-python-gdb-module.patch
|
2024-03-08 14:21:56 +00:00
|
|
|
|
|
|
|
|
# Not a backport. Add a new script which hooks into GDB and suggests
|
|
|
|
|
# RPMs to install when GDB finds an objfile with no debug info.
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch047: gdb-add-rpm-suggestion-script.patch
|
2024-01-29 22:55:13 +00:00
|
|
|
|
2024-05-15 20:17:34 +00:00
|
|
|
# Update x86 disassembler
|
2024-06-19 12:23:36 +00:00
|
|
|
Patch048: gdb-rhbz2277160-apx-disasm.patch
|
2024-05-15 20:17:34 +00:00
|
|
|
|
2024-07-05 13:57:56 +00:00
|
|
|
# backport of upstream commit 91874afabcd
|
|
|
|
|
# This (somehow) solves a double-free when reading minimal symbols
|
|
|
|
|
Patch049: gdb-rhel2295897-pre-read-DWZ-file-in-DWARF-reader.patch
|
|
|
|
|
|
