| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2020-12-07 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-06 | s390: Fix BC instruction breakpoint handling | Giancarlo Frix | 2 | -1/+6 | |
| This fixes a long-lived bug in the s390 port. When trying to step over a breakpoint set on a BC (branch on condition) instruction with displaced stepping on IBM Z, gdb would incorrectly adjust the pc regardless of whether or not the branch was taken. Since the branch target is an absolute address, this would cause the inferior to jump around wildly whenever the branch was taken, either crashing it or causing it to behave unpredictably. It turns out that the logic to handle BC instructions correctly was in the code, but that the enum value representing its opcode has always been incorrect. This patch corrects the enum value to the actual opcode, fixing the stepping problem. The enum value is also used in the prologue analysis code, so this also fixes a minor bug where more of the prologue would be read than was necessary. gdb/ChangeLog: PR breakpoints/27009 * s390-tdep.h (op_bc): Correct BC opcode value. | |||||
| 2020-12-06 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-05 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-04 | Update gdb/ChangeLog to reflect the PR for a bug fix | Shahab Vahedi | 1 | -0/+1 | |
| This is just an update in the gdb/ChangeLog to reflect a newly created PR [27015] for a bugfix commit: abaf3df9 arc: Write correct "eret" value during register collection | |||||
| 2020-12-04 | arc: Write correct "eret" value during register collection | Shahab Vahedi | 2 | -3/+12 | |
| In collect_register() function of arc-linux-tdep.c, the "eret" (exception return) register value was not being reported correctly. This patch fixes that. Background: When asked for the "pc" value, we have to update the "eret" register with GDB's STOP_PC. The "eret" instructs the kernel code where to jump back when an instruction has stopped due to a breakpoint. This is how collect_register() was doing so: --------------8<-------------- if (regnum == gdbarch_pc_regnum (gdbarch)) regnum = ARC_ERET_REGNUM; regcache->raw_collect (regnum, buf + arc_linux_core_reg_offsets[regnum]); -------------->8-------------- Root cause: Although this is using the correct offset (ERET register's), it is also changing the REGNUM itself. Therefore, raw_collect (regnum, ...) is not reading from "pc" anymore. v2: - Fix a copy/paste issue as rightfully addressed by Tom [1]. [1] https://sourceware.org/pipermail/gdb-patches/2020-November/173208.html gdb/ChangeLog: * arc-linux-tdep.c (collect_register): Populate "eret" by "pc" value from the regcache when asked for "pc" value. | |||||
| 2020-12-04 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-03 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-12-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-30 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-29 | Fix Value.format_string docu for static members argument | Hannes Domani | 2 | -1/+6 | |
| The argument is called static_members, not static_fields. gdb/doc/ChangeLog: 2020-11-29 Hannes Domani <ssbssa@yahoo.de> PR python/26974 * python.texi: Fix docu for static members argument. | |||||
| 2020-11-29 | Don't delete the locator win info | Hannes Domani | 2 | -1/+9 | |
| The locator win info is special because it is static, all the others are created dynamically. gdb/ChangeLog: 2020-11-29 Hannes Domani <ssbssa@yahoo.de> PR tui/26973 * tui/tui-layout.c (tui_apply_current_layout): Don't delete the static locator win info. | |||||
| 2020-11-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-24 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-23 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-17 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-16 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-15 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-14 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-13 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-12 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-11 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-10 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-09 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-08 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-07 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-06 | gdb: better static python detection in configure machinery | Romain Geissler | 3 | -2/+9 | |
| In python 3, itertools is a builtin module, so whether or not the python you link against is a shared or a static one, importing it works. Change the import test to use ctypes which is a dynamic module in both python 2 and 3. gdb/ChangeLog: PR python/26832 * configure: Regenerate. * configure.ac: Check for python modules ctypes instead of itertools. | |||||
| 2020-11-06 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-05 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-04 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-03 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-11-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-31 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-30 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2020-10-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
 |
index : riscv-gnu-toolchain/gdb.git | |
| Unnamed repository; edit this file 'description' to name the repository. | root |
| aboutsummaryrefslogtreecommitdiff |