aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2018-10-03Skip gdb ifunc tests on targets that don't support this feature.Sandra Loosemore4-3/+33
2018-10-03 Sandra Loosemore <sandra@codesourcery.com> * lib/gdb.exp (skip_ifunc_tests): New. * gdb.base/gnu-ifunc.exp: Skip if no ifunc support. Handle other compile failures. * gdb.compile/compile-ifunc.exp: Skip if no ifunc support.
2018-10-03Fix the handling of inlined frames in DWARF debug info.Millan Wolff3-6/+16
PR 23715 * dwarf2.c (find_abstract_instance): Allow recursive invocations of find_abstract_instance to override the name variable.
2018-10-03Updated French translation for the binutils/ subdirectory.Nick Clifton2-2008/+1911
2018-10-03Updated Portuguese translations for the bfd/ and binutils/ subdirectories.Nick Clifton4-5848/+5878
2018-10-03Make print_insn_s12z public.John Darrington2-0/+5
Gdb can use this function in its stack unwinder. * include/dis-asm.h (print_insn_s12z): Add declaration.
2018-10-02Use pulongest in aarch64-linux-tdep.cTom Tromey2-2/+6
I tried a build on macOS today and it failed due to a mismatch between the printf format and the type in aarch64-linux-tdep.c. This patch fixes the problem by using pulongest and %s rather than %ld. gdb/ChangeLog 2018-10-02 Tom Tromey <tom@tromey.com> * aarch64-linux-tdep.c (aarch64_linux_sigframe_init): Use pulongest.
2018-10-03Automatic date update in version.inGDB Administrator1-1/+1
2018-10-02RISC-V: Add fence.tso instructionPalmer Dabbelt7-0/+30
The RISC-V memory model has been ratified, and it includes an additional fence: "fence.tso". This pseudo instruction extends one of the previously reserved full fence patterns to be less restrictive, and therefor will execute correctly on all existing microarchitectures. Thus there is no reason to allow this instruction to be disabled (or unconverted to a full fence), so it's just unconditionally allowed. I've added a test case for GAS to check that "fence.tso" correctly assembles on rv32i-based targets. I checked to see that "fence.tso" appears in "gas.log", but that's the only testing I've done. gas/ChangeLog 2018-10-02 Palmer Dabbelt <palmer@sifive.com> * testsuite/gas/riscv/fence-tso.d: New file. * testsuite/gas/riscv/fence-tso.s: Likewise. include/ChangeLog 2018-10-02 Palmer Dabbelt <palmer@sifive.com> * opcode/riscv-opc.h (MATCH_FENCE_TSO): New define. (MASK_FENCE_TSO): Likewise. opcodes/ChangeLog 2018-10-02 Palmer Dabbelt <palmer@sifive.com> * riscv-opc.c (riscv_opcodes) <fence.tso>: New opcode.
2018-10-02Allow remote debugging over a Unix local domain socket.John Darrington9-2/+173
Extend the "target remote" and "target extended-remote" commands such that if the filename provided is a Unix local domain (AF_UNIX) socket, then it'll be treated as such, instead of trying to open it as if it were a character device. gdb/ChangeLog: * NEWS: Mention changed commands. * ser-uds.c: New file. * configure.ac (SER_HARDWIRE): Add ser-uds.o. * configure: Regenerate. * Makefile.in: Add new file. * serial.c (serial_open): Check if filename is a socket and lookup the appropriate interface accordingly. gdb/doc/ChangeLog: * gdb.texinfo (Remote Connection Commands): Describe the changes to target remote and target extended-remote relating to Unix domain sockets.
2018-10-02[ARC] Entries to Changelog for previous commits.Cupertino Miranda2-0/+21
2018-10-02Automatic date update in version.inGDB Administrator1-1/+1
2018-10-01Fix typo setting user_specified variable when parsing -Z option.Nick Clifton2-1/+7
PR 23698 * gprof.c (main): Fix typo setting user_specified variable when parsing -Z option.
2018-10-01Fix is_amd64_regs_target check in i386-avx512.expSimon Marchi2-2/+7
As reported by Jan here: https://sourceware.org/ml/gdb-patches/2018-09/msg00831.html the check that sets the number of available registers is backwards. gdb/testsuite/ChangeLog: * gdb.arch/i386-avx512.exp: Fix setting of nr_regs based on is_amd64_regs_target.
2018-10-01Add aarch64-sighandler-regs.exp testAlan Hayward4-0/+392
Add Aarch64 test to check register values of a previous frame can be shown correctly across a signal. gdb/testsuite/ChangeLog: * gdb.arch/aarch64-sighandler-regs.c: New test. * gdb.arch/aarch64-sighandler-regs.exp: New file. * lib/gdb.exp (skip_aarch64_sve_tests): New proc.
2018-10-01Aarch64: Detect FP regs in signal frameAlan Hayward2-19/+219
Both the VFP and SVE registers may be contained within the reserved space of the sigcontext and can be found by seraching for MAGIC values. Detect these and add the registers (including pseudos) to the trad frame cache. gdb/ * aarch64-linux-tdep.c (AARCH64_SIGCONTEXT_RESERVED_OFFSET): Add define. (AARCH64_EXTRA_MAGIC): Likewise. (AARCH64_FPSIMD_MAGIC): Likewise. (AARCH64_SVE_MAGIC): Likewise. (AARCH64_EXTRA_DATAP_OFFSET): Likewise. (AARCH64_FPSIMD_FPSR_OFFSET): Likewise. (AARCH64_FPSIMD_FPCR_OFFSET): Likewise. (AARCH64_FPSIMD_V0_OFFSET): Likewise. (AARCH64_FPSIMD_VREG_SIZE): Likewise. (AARCH64_SVE_CONTEXT_VL_OFFSET): Likewise. (AARCH64_SVE_CONTEXT_REGS_OFFSET): Likewise. (AARCH64_SVE_CONTEXT_P_REGS_OFFSET): Likewise. (AARCH64_SVE_CONTEXT_FFR_OFFSET): Likewise. (AARCH64_SVE_CONTEXT_SIZE): Likewise. (read_aarch64_ctx): Add function. (aarch64_linux_sigframe_init): Detect FP registers.
2018-10-01Aarch64: Move pseudo defines to headerAlan Hayward3-8/+23
gdb/ * aarch64-tdep.c (AARCH64_Q0_REGNUM): Move to here. (AARCH64_D0_REGNUM): Likewise. (AARCH64_S0_REGNUM): Likewise. (AARCH64_H0_REGNUM): Likewise. (AARCH64_B0_REGNUM): Likewise. (AARCH64_SVE_V0_REGNUM): Likewise. * arch/aarch64.h (AARCH64_Q0_REGNUM): Move from here. (AARCH64_D0_REGNUM): Likewise. (AARCH64_S0_REGNUM): Likewise. (AARCH64_H0_REGNUM): Likewise. (AARCH64_B0_REGNUM): Likewise. (AARCH64_SVE_V0_REGNUM): Likewise.
2018-10-01[ARC] Fixed issue with DTSOFF relocs.Cupertino Miranda3-4/+10
Inserted offset in final section in the GOT entry of type DTSOFF soon to be relocated by the dynamic loader. bfd/ 2018-09-06 Cupertino Miranda <cmiranda@synopsys.com> * arc-got.h (relocate_fix_got_relocs_for_got_info): Changed. Take TLS section alignment in consideration for this relocation. * elf32-arc.c (FINAL_SECTSTART): Added this formula macro. (ARC_TLS_DTPOFF) Updated reloc to use new created macro instead.
2018-10-01[ARC] Fixes TLS failures related to tls-align.Cupertino Miranda3-3/+10
This patch fixes glibc testcase in nptl/tls-align. bfd/ 2018-08-01 Cupertino Miranda <cmiranda@synopsys.com> * arc-got.h (relocate_fix_got_relocs_for_got_info): Changed, fixed TCB_SIZE offsize to include section alignment. * elf32-arc.c (arc_special_overflow_checks): Likewise. include/ 2018-08-01 Cupertino Miranda <cmiranda@synopsys.com> * arc-reloc.def (ARC_TLS_LE_32): Updated reloc formula.
2018-10-01[ARC] PLT information was still being generated when symbol was forced_local.Cupertino Miranda1-1/+2
A change upstream reveiled this issue, triggering an assert when linking glibc. bfd/ 2018-03-01 Cupertino Miranda <cmiranda@synopsys.com> * elf32-arc.c (elf_arc_check_relocs): Changed.
2018-10-01[ARC] Make sure global symbol is not an indirect or warning.Cupertino Miranda1-1/+6
Problem identified in the context of glibc with latest upstream binutils. Dynamic symbol space was being reserved but, no actual information for the symbol was being set. Data for the symbol was kept initialized with -1. No easy test case was possible to be created. bfd/ 2018-03-01 Cupertino Miranda <cmiranda@synopsys.com> * elf32-arc.c (elf_arc_check_relocs): Changed.
2018-10-01[ARC] Improved robustness. Return FALSE in case of NULL pointer.Cupertino Miranda1-0/+3
bfd/ 2018-03-01 Cupertino Miranda <cmiranda@synopsys.com> * elf32-arc.c (elf_arc_finish_dynamic_symbol) Return FALSE in case arc_htab is NULL.
2018-10-01[ARC] Refactored location where GOT information is collected.Cupertino Miranda2-37/+46
Change location where GOT information is collected for ARC target, avoiding posible use conflicts of the previous .got field in the symbols hash_entry. bfd/ 2018-03-01 Cupertino Miranda <cmiranda@synopsys.com> * arc-got.h (get_got_entry_list_for_symbol): Changed. * ef32-arc.c (struct elf_arc_link_hash_entry): Moved and changed. (elf_arc_link_hash_newfunc): Changed. (arc_elf_link_hash_table_create): Removed old initializations. (elf_arc_relocate_section, elf_arc_finish_dynamic_symbol): Changed.
2018-10-01Remove ancient workaroundGary Benson6-87/+11
This commit removes a workaround for a bug in glibc 2.1.3, which was released 2000-02-24 and superseded 2000-11-09. gdb/ChangeLog: * gdb_proc_service.h (gdb_prfpregset_t): Remove typedef. * proc-service.c (ps_lgetfpregs, ps_lsetfpregs): Use prfpregset_t instead of gdb_prfpregset_t. * configure.ac (PRFPREGSET_T_BROKEN): Remove check. * configure, config.in: Rebuild.
2018-10-01Move duplicated code to common/gdb_proc_service.hGary Benson6-300/+187
This commit moves now-identical code from gdb/gdb_proc_service.h and gdb/gdbserver/gdb_proc_service.h into the new shared file gdb/common/gdb_proc_service.h. gdb/ChangeLog: * common/gdb_proc_service.h: New file, factored out from... * gdb_proc_service.h: Moved common code to the above file. * Makefile.in (HFILES_NO_SRCDIR): Add the above new file. gdb/gdbserver/ChangeLog: * gdb_proc_service.h: Moved common code to common/gdb_proc_service.h.
2018-10-01Update GDB gdb_proc_service.h workaround to match gdbserverGary Benson2-2/+7
This commit updates GDB's gdb_proc_service.h to use elf_{g,fp}regset_t instead of gdb_{g,fp}regset_t if pr{g,fp}regset_t are undefined. The types have been equivalent on GNU/Linux since at least 2005. gdb/ChangeLog: * gdb_proc_service.h: Use elf_gregset_t if prgregset_t is undefined. Use elf_fpregset_t if prfpregset_t is undefined.
2018-10-01Add workaround from gdbserver's gdb_proc_service.h to GDBGary Benson5-2/+63
This commit adds a workaround from gdbserver's gdb_proc_service.h to GDB's. It doesn't seem to have been needed on any glibc as far back as 2001, but it's possibly required for other C libraries so I've retained it. gdb/ChangeLog: * configure.ac: Check if sys/procfs.h defines elf_fpregset_t. (AC_CHECK_HEADERS): Check for linux/elf.h. * configure, config.in: Rebuild. * gdb_proc_service.h: Include linux/elf.h if sys/procfs.h doesn't define elf_fpregset_t.
2018-10-01gdb_proc_service.h comment and whitespace synchronizationGary Benson4-9/+42
This commit updates comments and whitespace in GDB's and gdbserver's gdb_proc_service.h. gdb/ChangeLog: * gdb_proc_service.h: Whitespace change. gdb/gdbserver/ChangeLog: * gdb_proc_service.h: Synchronize comments and whitespace with GDB's version of this file.
2018-10-01Don't check HAVE_UNISTD_HTom Tromey4-15/+9
I noticed some spots that were checking HAVE_UNISTD_H. There is no need to do this, as <unistd.h> is unconditionally included in many places in gdb. This sort of cleanup was done once before, in 2013: 2013-07-01 Pedro Alves <palves@redhat.com> * defs.h: Don't check HAVE_UNISTD_H before including <unistd.h>. (STDIN_FILENO, STDOUT_FILENO, STDERR_FILENO): Delete. * tracepoint.c: Don't check HAVE_UNISTD_H before including <unistd.h>. HAVE_UNISTD_H seems to come from gnulib, so there are still mentions of it in the source. gdb/ChangeLog 2018-10-01 Tom Tromey <tom@tromey.com> * unittests/scoped_mmap-selftests.c: Don't check HAVE_UNISTD_H. * unittests/scoped_fd-selftests.c: Don't check HAVE_UNISTD_H. * common/scoped_fd.h: Don't check HAVE_UNISTD_H.
2018-10-01Copy configure option documentation to gdb.texinfoTom Tromey4-5/+160
I realized that while I'd updated the README, I didn't update gdb.texinfo to document the options to configure. This patch copies the text from README into gdb.texinfo, adding Texinfo markup. gdb/ChangeLog 2018-10-01 Tom Tromey <tom@tromey.com> * README: Minor change. gdb/doc/ChangeLog 2018-10-01 Tom Tromey <tom@tromey.com> * gdb.texinfo (Configure Options): Document configure options.
2018-10-01testsuite: fix is_amd64_regs_targetMarkus Metzger2-6/+12
Commit c221b2f Testsuite: Add gdb_can_simple_compile changed the source file name extension of the test program from .s to .c resulting in compile fails. This, in turn, causes is_amd64_regs_target checks to fail. In gdb.btrace/tailcall.exp and others, this causes the wrong source file to be picked and the test to fail on 64-bit targets. Change the test source from an assembly program to a C program using inline assembly. testsuite/ * lib/gdb.exp (is_amd64_regs_target): Change assembly to C inline assembly.
2018-10-01Automatic date update in version.inGDB Administrator1-1/+1
2018-09-30Darwin: Remove unused variables [-Werror=unused-variable]Pedro Alves4-37/+14
Building GDB with --host=x86_64-apple-darwin15 using G++ 5.3.0 runs into a number of -Werror=unused-variable warnings/errors: ../../src/gdb/i386-darwin-nat.c: In function 'void i386_darwin_dr_set(int, CORE_ADDR)': ../../src/gdb/i386-darwin-nat.c:283:7: error: unused variable 'current_pid' [-Werror=unused-variable] int current_pid; ^ [etc, etc.] This commit fixes all such warnings. gdb/ChangeLog: 2018-09-30 Pedro Alves <palves@redhat.com> * darwin-nat-info.c (darwin_debug_regions_recurse) (info_mach_exceptions_command): Remove unused local variables. * darwin-nat.c (darwin_decode_notify_message) (darwin_nat_target::resume, darwin_nat_target::mourn_inferior) (darwin_stop_inferior, darwin_setup_exceptions) (darwin_nat_target::kill, darwin_attach_pid, darwin_ptrace_him) (darwin_nat_target::attach, darwin_nat_target::detach) (darwin_read_write_inferior, darwin_read_dyld_info): Remove unused local variables. * i386-darwin-nat.c (i386_darwin_dr_set): Remove unused local variables.
2018-09-30Automatic date update in version.inGDB Administrator1-1/+1
2018-09-29Remove some leftover text in gdb/READMETom Tromey2-3/+4
I accidentally left some stray text in gdb/README. This removes it. I'm checking this in as obvious. gdb/ChangeLog 2018-09-29 Tom Tromey <tom@tromey.com> * README: Remove some leftover text.
2018-09-29Update gdb's configure instructionsTom Tromey5-182/+208
gdb's README and configure instructions in the manual are quite out of date. They mention options that haven't existed for many years, among other things. This patch attempts to modernize the instructions somewhat. It is not exhaustive, just an improvement -- more could be done. Perhaps even a couple of the nodes should simply be removed and replaced by references to the Autoconf manual. The README file seems to have been generated from the Texinfo at some point in the past. I did not continue this, but instead edited it separately. gdb/ChangeLog 2018-09-29 Tom Tromey <tom@tromey.com> * PROBLEMS: Rewrite. * README: Update. gdb/doc/ChangeLog 2018-09-29 Tom Tromey <tom@tromey.com> * gdb.texinfo (Requirements): Mention C++, GNU make. (Requirements): Sort the table. Add more libraries. (Running Configure): Remove obsolete text. (Separate Objdir): Likewise. (Configure Options): Likewise.
2018-09-29Automatic date update in version.inGDB Administrator1-1/+1
2018-09-28bfd: Use elfclass instead of bed->s->elfclassH.J. Lu2-2/+7
elfclass has been set to bed->s->elfclass earlier. * elf-properties.c (_bfd_elf_link_setup_gnu_properties): Use elfclass instead of bed->s->elfclass.
2018-09-28Use the existing instruction to determine the RISC-V breakpoint kind.John Baldwin3-20/+49
RISC-V supports instructions of varying lengths. Standard existing instructions in the base ISA are 4 bytes in length, but the 'C' extension adds support for compressed, 2 byte instructions. RISC-V supports two different breakpoint instructions: EBREAK is a 4 byte instruction in the base ISA, and C.EBREAK is a 2 byte instruction only available on processors implementing the 'C' extension. Using EBREAK to set breakpoints on compressed instructions causes problems as the second half of EBREAK will overwrite the first 2 bytes of the following instruction breaking other threads in the process if their PC is the following instruction. Thus, breakpoints on compressed instructions need to use C.EBREAK instead of EBREAK. Previously, the riscv architecture checked the MISA register to determine if the 'C' extension was available. If so, it used C.EBREAK for all breakpoints. However, the MISA register is not necessarily available to supervisor mode operating systems. While native targets could provide a fake MISA register value, this patch instead examines the existing instruction at a breakpoint target to determine which breakpoint instruction to use. If the existing instruction is a compressed instruction, C.EBREAK is used, otherwise EBREAK is used. gdb/ChangeLog: * disasm-selftests.c (print_one_insn_test): Add bfd_arch_riscv to case with explicit breakpoint kind. * riscv-tdep.c (show_use_compressed_breakpoints): Remove 'additional_info' and related logic. (riscv_debug_breakpoints): New variable. (riscv_breakpoint_kind_from_pc): Use the length of the existing instruction to determine the breakpoint kind. (_initialize_riscv_tdep): Add 'set/show debug riscv breakpoints' flag. Update description of 'set/show riscv use-compressed-breakpoints' flag.
2018-09-28Change "xor" name in cpu_core to allow building with iso646.h or C++ compilerКомпан, Вячеслав Олегович3-4/+14
This code was introduced back in 1998, and C99 appeared next year, defining the `xor` as an 'alternative keyword' if iso646.h is included. Moreover, C++98 defines it on the language level. As a result, the code is not buildable with C++ compiler or if iso646.h is included beforehand. According to comment, `sim_cpu_core` is mostly a clone of `sim_core`, so I renamed it to `byte_xor` as it's called in `sim_core`. sim/common/ChangeLog: * sim-core.h (sim_cpu_core): Rename cpu_core.xor to cpu_core.byte_xor. * sim-core.c (sim_core_set_xor): Likewise. (sim_core_xor_read_buffer): Likewise. (sim_core_xor_write_buffer): Likewise.
2018-09-28gdb: Change how frames are selected for 'frame' and 'info frame'.Andrew Burgess12-208/+870
The 'frame' command, and thanks to code reuse the 'info frame' and 'select-frame' commands, currently have an overloaded mechanism for selecting a frame. These commands take one or two parameters, if it's one parameter then we first try to use the parameter as an integer to select a frame by level (or depth in the stack). If that fails then we treat the parameter as an address and try to select a stack frame by stack-address. If we still have not selected a stack frame, or we initially had two parameters, then GDB allows the user to view a stack frame that is not part of the current backtrace. Internally, a new frame is created with the given stack and pc addresses, and this is shown to the user. The result of this is that a typo by the user, entering the wrong stack frame level for example, can result in a brand new frame being viewed rather than an error. The purpose of this commit is to remove this overloading, while still offering the same functionality through some new sub-commands. By making the default behaviour of 'frame' (and friends) be to select a stack frame by level index, it is hoped that enough backwards-compatibility is maintained that users will not be overly inconvenienced. The 'frame', 'select-frame', and 'info frame' commands now all take a frame specification string as an argument, this string can be any of the following: (1) An integer. This is treated as a frame level. If a frame for that level does not exist then the user gets an error. (2) A string like 'level <LEVEL>', where <LEVEL> is a frame level as in option (1) above. (3) A string like 'address <STACK-ADDRESS>', where <STACK-ADDRESS> is a stack-frame address. If there is no frame for this address then the user gets an error. (4) A string like 'function <NAME>', where <NAME> is a function name, the inner most frame for function <NAME> is selected. If there is no frame for function <NAME> then the user gets an error. (5) A string like 'view <STACK-ADDRESS>', this views a new frame with stack address <STACK-ADDRESS>. (6) A string like 'view <STACK-ADDRESS> <PC-ADDRESS>', this views a new frame with stack address <STACK-ADDRESS> and the pc <PC-ADDRESS>. This change assumes that the most common use of the commands like 'frame' is to select a frame by frame level, it is for this reason that this is the behaviour that is kept for backwards compatibility. Any of the alternative behaviours, which are assumed to be less used, now require a change in user behaviour. The MI command '-stack-select-frame' has not been changed. This ensures that we maintain backwards compatibility for existing frontends. gdb/ChangeLog: (NEWS): Mention changes to frame related commands. * cli/cli-decode.c (add_cmd_suppress_notification): New function. (add_prefix_cmd_suppress_notification): New function. (add_com_suppress_notification): Call add_cmd_suppress_notification. * command.h (add_cmd_suppress_notification): Declare. (add_prefix_cmd_suppress_notification): Declare. * mi/mi-cmd-stack.c: Add 'safe-ctype.h' include. (parse_frame_specification): Moved from stack.c, with simplification to handle a single argument. (mi_cmd_stack_select_frame): Use parse_frame_specification, the switch to the selected frame. Add a header comment. * stack.c: Remove 'safe-ctype.h' include. (find_frame_for_function): Add declaration. (find_frame_for_address): New function. (parse_frame_specification): Moved into mi/mi-cmd-stack.c. (frame_selection_by_function_completer): New function. (info_frame_command): Rename to... (info_frame_command_core): ...this, and update parameter types. (select_frame_command): Rename to... (select_frame_command_core): ...this, and update parameter types. (frame_command): Rename to... (frame_command_core): ...this, and update parameter types. (class frame_command_helper): New class to wrap implementations of frame related sub-commands. (frame_apply_cmd_list): New static global. (frame_cmd_list): Make static. (select_frame_cmd_list): New global for sub-commands. (info_frame_cmd_list): New global for sub-commands. (_initialize_stack): Register sub-commands for 'frame', 'select-frame', and 'info frame'. Update 'frame apply' commands to use frame_apply_cmd_list. Move function local static frame_apply_list to file static frame_apply_cmd_list for consistency. * stack.h (select_frame_command): Delete declarationn. (select_frame_for_mi): Declare new function. gdb/doc/ChangeLog: * gdb.texinfo (Frames): Rewrite the description of 'frame number' to highlight that the number is also the frame's level. (Selection): Rewrite documentation for 'frame' and 'select-frame' commands. (Frame Info): Rewrite documentation for 'info frame' command. gdb/testsuite/ChangeLog: * gdb.base/frame-selection.exp: New file. * gdb.base/frame-selection.c: New file.
2018-09-27RISC-V: Pc-rel to gp-rel relaxation function cleanup.Jim Wilson2-42/+32
bfd/ * elfnn-riscv.c (riscv_init_pcgp_relocs): Add explanatory comment. (riscv_free_pcgp_relocs, riscv_record_pcgp_reloc): Likewise. (riscv_find_pcgp_hi_reloc, riscv_reocrd_pcgp_lo_reloc): Likewise. (riscv_find_pcgp_lo_reloc): Likewise. (riscv_delete_pcgp_hi_reloc, riscv_use_pcgp_hi_reloc): Delete. (riscv_delete_pcgp_lo_reloc): Likewise. (_bfd_riscv_relax_pc): Don't call riscv_use_pcgp_hi_reloc. Replace calls to riscv_delete_pcgp_lo_reloc and riscv_delete_pcgp_hi_reloc with TRUE. Mark abfd arg as ATTRIBUTE_UNUSED.
2018-09-28Automatic date update in version.inGDB Administrator1-1/+1
2018-09-27testsuite: Fix race condition in check-libthread-dbAlan Hayward2-0/+14
It is possible for the created thread to reach the breakpoint before the main thread has set errno to 23. Prevent this using a pthread barrier. * gdb.threads/check-libthread-db.c (thread_routine): Use a pthread barrier. (main): Likewise.
2018-09-27Automatic date update in version.inGDB Administrator1-1/+1
2018-09-26Skip broken assembler test on Windows host.Sandra Loosemore2-1/+10
2018-09-26 Sandra Loosemore <sandra@codesourcery.com> gas/ * testsuite/gas/all/gas.exp: Skip "Output file must be distinct from input" test on Windows host.
2018-09-26gdb/riscv: Improve non-dwarf stack unwindingAndrew Burgess7-21/+189
This commit improves the prologue scanning stack unwinder, to better support AUIPC, LUI, and more variants of ADD and ADDI. This allows unwinding over frames containing large local variables, where the frame size does not fit into a single instruction immediate, and is first loaded into a temporary register, before being added to the stack pointer. A new test is added that tests this behaviour. As there's nothing truely RiscV specific about this test I've added it into gdb.base, but as this depends on target specific code to perform the unwind it is possible that some targets might fail this new test. gdb/ChangeLog: * riscv-tdep.c (riscv_insn::decode): Decode c.lui. (riscv_scan_prologue): Split handling of AUIPC, LUI, ADD, ADDI, and NOP. gdb/testsuite/ChangeLog: * gdb.base/large-frame-1.c: New file. * gdb.base/large-frame-2.c: New file. * gdb.base/large-frame.exp: New file. * gdb.base/large-frame.h: New file.
2018-09-26elf32-nds32: Remove elf32_nds32_allocate_dynrelocsSimon Marchi2-13/+4
It is unused, removing it fixes this error when building with clang: /home/emaisin/src/binutils-gdb/bfd/elf32-nds32.c:3172:1: error: unused function 'elf32_nds32_allocate_dynrelocs' [-Werror,-Wunused-function] elf32_nds32_allocate_dynrelocs (struct bfd_link_info *info, asection *sreloc, ^ 1 error generated. gcc only reports the error if you remove "inline". I don't know if this is actually a mistake and it should actually be used though. gdb/ChangeLog: * elf32-nds32.c (elf32_nds32_allocate_dynrelocs): Remove.
2018-09-26Remove dead definition from valops.cTom Tromey2-7/+4
This removes a variable definition in valops.c that has been surrounded by "#if 0" since gdb moved to sourceware. gdb/ChangeLog 2018-09-26 Tom Tromey <tom@tromey.com> * valops.c (auto_abandon): Remove dead code.
2018-09-26Small fix for "winheight" usageTom Tromey2-1/+5
I noticed that the usage string for "winheight" has a couple of extraneous ">"s in it. I must have forgotten to remove these back when I changed the text to use the GNU style for metasyntactic variables. gdb/ChangeLog 2018-09-26 Tom Tromey <tom@tromey.com> * tui/tui-win.c (WIN_HEIGHT_USAGE): Remove extra ">"s.
2018-09-26Automatic date update in version.inGDB Administrator1-1/+1
generated by cgit v1.1 at 2024-09-13 22:39:46 +0000